7.

SYSTEM TESTING

System testing is a critical aspect of Software Quality Assurance and represents the
ultimate review of specification, design and coding. Testing is a process of executing a program
with the intent of finding an error. A good test is one that has a probability of finding an as yet
undiscovered error. The purpose of testing is to identify and correct bugs in the developed
system. Nothing is complete without testing. Testing is the vital to the success of the system.
Software testing is an investigation conducted to provide stakeholders with information about the
quality of the product or service under test. Software testing can also provide an objective,
independent view of the software to allow the business to appreciate and understand the risks of
software implementation. Test techniques include, but are not limited to the process of executing
a program or application with the intent of finding software bugs (errors or other defects).
Testing is vital to the success of the system. System testing marks a logical assumption that all
the parts of the system are correct; the goal successfully achieved. Special test data is input for
processing and the results are examined to locate unexpected results.
 Software reliability, quality, System assurance
 Identifying and Preventing the defects
 Make sure the software met the user requirements
 Gaining confidence about the level of quality and providing information
 Tells about the risk of releasing the system at the given time
 Verification and Validation.

Unit Testing
Unit testing focuses on verification effort on the smallest unit of software design. This
testing includes testing of control paths, interfaces, local data structures, logical decisions,
boundary conditions, and error handling. Unit testing may use Test Drivers, which are control
programs to co-ordinate test case inputs and outputs, which replace low-level modules. The
white-box testing techniques were heavily employed for unit testing. It tests all of the methods
involved in this system and checks the output of each event.
Integration Testing
Integration testing is systematic technique for constructing the program structure while at
the same time conducting tests to uncover error associated with interfacing. The objective is to
take unit modules and build a program structure that has been directed by design. Top-Down
integration and Bottom-up Integration are tested finally. After each module was successfully
tested, tests were carried out on the integrated application as a whole to analyze the interaction of
various modules with each other as well the working of each individual module in an integrated
application.

Acceptance Testing

At last the system is delivered to the user for Acceptance testing and after checking all
the need of the users.

Software Testing

Software testing is the process of evaluation a software item to detect differences

between given input and expected output also to assess the feature of a software item. Testing
assesses the quality of the product. Software testing is a process that should be done during the
development process. In other words software testing is a verification and validation process.

Verification Testing

Verification is the process to make sure the product satisfies the conditions imposed at
the start of the development phase. In other words, to make sure the product behaves the way we
want it to.

Validation Testing

Validation is the process to make sure the product satisfies the specified requirements at
the end of the development phase. In other words, to make sure the product is built as per
customer requirements.
Basics of software testing

There are two basics of software testing: black box testing and white box testing.

Black box Testing

Black box testing is a testing technique that ignores the internal mechanism of the system
and focuses on the output generated against any input and execution of the system. It is also
called functional testing.
White box Testing
White box testing is a testing technique that takes into account the internal mechanism of
a system. It is also called structural testing and glass box testing.
Black box testing is often used for validation and white box testing is often used for verification.

Stress Testing
Stress testing is the testing to evaluate how system behaves under unfavorable conditions.
Testing is conducted at beyond limits of the specifications. It falls under the class of black box
testing.

Usability Testing
Usability testing is performed to the perspective of the client, to evaluate how the GUI is
user-friendly? How easily can the client learn? After learning how to use, how proficiently can
the client perform? How pleasing is it to use its design? This falls under the class of black box
testing.

Regression Testing
Regression testing is the testing after modification of a system, component, or a group of
related units to ensure that the modification is working correctly and is not damaging or
imposing other modules to produce unexpected results. It falls under the class of black box
testing.

Functional Testing
 This type of testing ignores the internal parts and focus on the output is as per requirement
or not. Black-box type testing geared to functional requirements of an application.

End-to-End Testing
Similar to system testing, involves testing of a complete application environment in a
situation that mimics real-world use, such as interacting with a database, using network
communications, or interacting with other hardware, applications, or systems if appropriate.
White box Testing
White box testing is a testing technique that takes into account the internal mechanism of
a system. It is also called structural testing and glass box testing.
Black box testing is often used for validation and white box testing is often used for verification.

Stress Testing
Stress testing is the testing to evaluate how system behaves under unfavorable conditions.
Testing is conducted at beyond limits of the specifications. It falls under the class of black box
testing.

Bottom up Integration Testing

In bottom up integration testing, module at the lowest level are developed first and other
modules which go towards the 'main' program are integrated and tested one at a time. It is
usually performed by the testing teams.

Branch Testing
Testing technique in which all branches in the program source code are tested at least
once. This is done by the developer.

Interface Testing
Testing conducted to evaluate whether systems or components pass data and control
correctly to one another. It is usually performed by both testing and development teams.
Operational Testing
Testing technique conducted to evaluate a system or component in its operational
environment. Usually it is performed by testing teams.

Performance Testing
Functional testing conducted to evaluate the compliance of a system or component with
specified performance requirements. It is usually conducted by the performance engineer.

Qualification Testing
Testing against the specifications of the previous release, usually conducted by the developer
for the consumer, to demonstrate that the software meets its specified requirements.

Security Testing
A process to determine that an information system protects data and maintains
functionality as intended. It can be performed by testing teams or by specialized security-testing
companies.

Upgrade Testing
Testing technique that verifies if assets created with older versions can be used properly
and that user's learning is not challenged. It is performed by the testing teams.

User Interface Testing

Type of testing which is performed to check how user-friendly the application is. It is
performed by testing teams.