Testing the behavior of the whole software/system as defined in software requirements specification (SRS) is known as system testing. Its main focus is to verify that the customer requirements are fulfilled. System testing is done after integration testing is complete. System testing should test functional and non functional requirements of the software.
Why System Testing is required?
System Testing is a crucial step in Quality Management Process.
- In the Software Development Life cycle System Testing is the first level where the System is tested as a whole
- The System is tested to verify if it meets the functional and technical requirements
- The application/System is tested in an environment that closely resembles the production environment where the application will be finally deployed
- The System Testing enables us to test, verify and validate both the Business requirements as well as the Application Architecture
Prerequisites for System Testing:
- Unit Testing must be completed
- Integration Testing must be completed
- Complete software system should be developed
- A software testing environment that closely resembling the production environment must be available.
System testing in seven steps:
- Creation of System Test Plan
- Creation of system test cases
- Selection / creation of test data for system testing
- Software Test Automation of execution of automated test cases
- Execution of test cases
- Bug fixing and regression testing
- Repeat the software test cycle
How to write a System Test Case?
A Test Case describes exactly how the test should be carried out. The System test cases help us verify and validate the system. The System Test Cases are written such that:
- They cover all the use cases and scenarios
- The Test cases validate the technical Requirements and Specifications
- The Test cases verify if the application/System meet the Business & Functional Requirements specified
- The Test cases may also verify if the System meets the performance standards
