SYSTEM TESTING

WHAT IS SYSTEM TESTING?

Integrating components to create the version of
the system and testing the integrated system.
Checks for the compatibility between components,
the right interaction between them, and the right
transfer of data at the right time.

Integration testing Vs System Testing.

System Testing Vs Component Testing.

TYPES OF SYSTEM TESTING

1
FUNCTIONAL TESTING
Validation of functional
requirements

2
NON-FUNCTIONAL TESTING
Validation of non-functional
requirements

ENTRY CRITERIA
FOR SYSTEM TESTING
Unit testing should be finished.
Modules should be integrated.

Software development is completed based on

specifications document
Testing environment is available for testing

HOW TO DO A SYSTEM TEST

1

Prepare a system test plan

2 Creation of test cases

3 Creation of test data used for the system testing

4 Execution of test cases
5 Bug reporting and bug verification
6 Repeat testing life cycle if required

USER TESTING
This is the stage in the testing process in which
users or customers provide input and advice on
system testing.

TYPES OF USER TESTING

Users of the software work with the
development team near the end

Alpha Testing

of completion to test the

software at the developers site.

Release of the software is made

available to users to allow them to

Beta Testing

experiment and to raise problems

that they discover with the system
developers.
Customers test a system to decide
whether or not it is ready to be

Acceptance Testing

accepted from the system

developers and deployed in the
customer environment.

Alpha testing may precede Beta testing! :D

ACCEPTANCE TESTING
An inherent part of custom systems development.

Takes place after release testing.

Acceptance implies that payment should be made for the system.

ACCEPTANCE TESTING STEPS

1

Define acceptance criteria

Plan acceptance testing

[requirements | things needed | risks]

Derive acceptance testing

Implement acceptance test

Negotiate test results

Reject/Accept System