Scribd
Upload
25 views4 pages

Overview of System Testing Types

The document outlines the purpose and types of software testing, emphasizing the importance of discovering errors and ensuring functionality meets requirements. It details various testing methods including unit testing, integration testing, functional testing, system testing, white box testing, and black box testing, each serving specific objectives. Additionally, it highlights the significance of user acceptance testing and reports successful test results with no defects encountered.

Uploaded by

Jaya Raj
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
25 views4 pages

Overview of System Testing Types

The document outlines the purpose and types of software testing, emphasizing the importance of discovering errors and ensuring functionality meets requirements. It details various testing methods including unit testing, integration testing, functional testing, system testing, white box testing, and black box testing, each serving specific objectives. Additionally, it highlights the significance of user acceptance testing and reports successful test results with no defects encountered.

Uploaded by

Jaya Raj
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

SYSTEM TESTING

The purpose of testing is to discover errors. Testing is the process of trying to discover every
conceivable fault or weakness in a work product. It provides a way to check the functionality of
components, sub-assemblies, assemblies and/or a finished product It is the process of exercising
software with the intent of ensuring that the

Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific
testing requirement.

TYPES OF TESTS
Unit testing
Unit testing involves the design of test cases that validate that the internal program
logic is functioning properly, and that program inputs produce valid outputs. All decision
branches and internal code flow should be validated. It is the testing of individual software
units of the application .it is done after the completion of an individual unit before
integration. This is a structural testing, that relies on knowledge of its construction and is
invasive. Unit tests perform basic tests at component level and test a specific business
process, application, and/or system configuration.

Unit

tests ensure that each unique path of a business process performs accurately to the
documented specifications and contains clearly defined inputs and expected results.

Integration testing
Integration tests are designed to test integrated software components to determine if
they actually run as one program. Testing is event driven and is more concerned with the
basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the
combination of components is correct and consistent. Integration testing is specifically aimed
at exposing the problems that arise from the combination of components.
Functional test
Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user
manuals.

Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key


functions, or special test cases. In addition, systematic coverage pertaining to identify
Business process flows; data fields, predefined processes, and successive processes must be
considered for testing. Before functional testing is complete, additional tests are identified
and the effective value of current tests is determined.

System Test
System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system testing is
the configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.

White Box Testing


White Box Testing is a testing in which in which the software tester has knowledge of
the inner workings, structure and language of the software, or at least its purpose. It is
purpose. It is used to test areas that cannot be reached from a black box level.

Black Box Testing


Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of tests,
must be written from a definitive source document, such as specification or requirements
document, such as specification or requirements document. It is a testing in which the
software under test is treated, as a black box. you cannot “see” into it. The test provides
inputs and responds to outputs without considering how the software works.

6.1 Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be conducted as
two distinct phases.

Test strategy and approach


Field testing will be performed manually and functional tests will be written in detail.
Test objectives
 All field entries must work properly.
 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.

Features to be tested
 Verify that the entries are of the correct format
 No duplicate entries should be allowed
 All links should take the user to the correct page.

6.2 Integration Testing


Software integration testing is the incremental integration testing of two or more
integrated software components on a single platform to produce failures caused by interface
defects.

The task of the integration test is to check that components or software applications,
e.g. components in a software system or – one step up – software applications at the company
level – interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

6.3 Acceptance Testing


User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.
Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

Common questions

Powered by AI

Testing based on "pre-driven process links and integration points" is crucial in system testing as it ensures that the system's individual components interact correctly and consistently within the defined workflows and integration requirements. This approach helps identify issues in process flows, dependencies, and sequence of operations that can only be detected once the system operates as a cohesive unit .

Functional tests systematically demonstrate that specific functions operate as specified by the business and technical requirements . The scope focuses on individual features, inputs/outputs, and interactions. System tests, however, have a broader scope, ensuring that the entire integrated system meets all requirements and functions well together, usually testing based on higher-level process flows and integration points .

Unit testing ensures correct functioning by validating that internal program logic is functioning properly such that expected inputs produce valid outputs. It focuses on testing individual components in isolation . In contrast, integration testing evaluates the interaction between integrated software components, specifically targeting issues caused by interface defects .

Process descriptions and flows play a central role in system testing by outlining expected interactions and integration points within the software system. They provide a structured framework for testing, ensuring that testing is conducted systematically along predefined paths. This contributes to the testing process by revealing possible discrepancies or integration issues, helping ensure alignment with desired operational flows and system architecture .

Black-box testing evaluates software without knowledge of its internal structure, ideal for validating functionality against requirements and ensuring that input-output flows are correct . Its primary advantage is testing the system comprehensively from a user-like perspective. White-box testing, on the other hand, involves testing software with an understanding of its internal workings, which helps to identify internal code issues that are inaccessible through black-box methods. It is advantageous for ensuring the correctness of internal logic and structure .

White-box testing complements black-box testing by addressing the limitations of each type. While black-box testing focuses on verifying the software's behavior against specifications without internal system knowledge, white-box testing delves into the software's internals, examining logic, loops, and code paths to find defects that are not visible in black-box testing. By combining both, testers can achieve comprehensive defect detection; covering everything from user interface errors to deeper structural issues .

Integration testing is essential for ensuring reliability by validating that integrated software components function correctly as a combined unit. It primarily addresses the challenges of interface defects and interaction errors that can occur when independently tested components are brought together. This phase uncovers issues related to dependencies, data exchange, and system architecture integrity .

Functional test preparation focuses on systematic coverage by organizing tests around requirements, key functions, and special test cases . It addresses valid and invalid inputs, functionality testing, output validation, and testing interfacing systems or procedures, ensuring that business processes and their successive steps are thoroughly verified .

User acceptance testing focuses primarily on ensuring that the system meets functional requirements from an end-user perspective . Significant user participation is critical because it verifies that the developed system aligns closely with user expectations and business needs, bridging the gap between developers' understanding and practical user requirements .

The fundamental purpose of system testing is to ensure that the entire integrated software system meets its requirements and produces predictable results based on process descriptions and flows, emphasizing pre-driven process links and integration points .

You might also like