SYSTEM TESTING

System Testing is the testing of a complete and fully integrated software product.
Usually, software is the only one element of a larger computer-based system. Ultimately,
software is interfaced with other software or hardware systems. System Testing is actually a
series of different tests whose sole purpose is to exercise the full computer-based system.
System implementation is the process of defining how the information system should
be built (physical system design), ensuring that the information system is operational and
used, ensuring that the information system meets quality standard (quality assurance). This
successful implementation of the new system depends upon the involvement of staff working
in the department.
The testing steps are:

 Unit testing
 Integration testing
 Acceptance testing
 Validation testing

UNIT TESTING

Unit testing is a software development process in which the smallest testable parts of
an application, called units, are individually and independently scrutinized for proper
operation. Unit testing can be done manually but is often automated. In computer
programming, unit testing is a software testing method by which individual units of source
code, sets of one or more computer program modules together with associated control data,
usage procedures, and operating procedures, are tested to determine whether they are fit for
use. All independent paths through the control structures in a module are executed at least
once.
INTEGRATION TESTING

Integration testing (sometimes called integration and testing, abbreviated I&T) is the
phase in software testing in which individual software modules are combined and tested as a
group. It occurs after unit testing and validation testing. Integration testing takes as its input
modules that have been unit tested, groups them in larger aggregates, applies test defined in
an integration test plan to those aggregates, and delivers as its output the integrated system
ready for system testing.

VALIDATION TESTING

Validation testing ensures that the product actually meets the client’s needs. It can
also be defined as to determine that the product fulfils its intended use when deployed on
appropriate environment. After the termination of integration testing, software is completely
assembled as a package. Interfacing errors are uncovered and corrected in a final series of
software test validation. Software validation is achieved through a series of black drops
which is a test that demonstrate conformity with requirements. After validation test has been
conducted one of the two best condition exits.
 The functions of performance characteristics confirm to specification are accepted.
 Validation form specification is uncovered and a deficiency is created.

 Deviation or error discovered at this step in the project is corrected prior to the project
completion.

ACCEPTANCE TESTING

Acceptance testing involves planning and execution of functional test. This testing
technique is performed to determine whether or not the software system has met the
requirement specifications. The main purpose of this test is to evaluate the system’s
compliance with the business requirements and verify if it had met the required criteria for
delivery to end users.

There are various forms of acceptance testing:

 User acceptance Testing
 Business acceptance Testing
 Alpha Testing