What is System Testing?
After completion of softwareand integration testing, the development team is releasing a software build to engineer team.
The testing team is conducting system testing on that software in two sub levels such as
- Functional Testing
- Non-Functional Testing
Functional testing is concentrating on customer requirements and the Non-Functional testing is concentrating on customer expectations.
Functional Testing: It’s a mandatory testing level, during this test the testing team is validating a software build functionality in terms of below factors with respect to customer requirements.
- Behavioral / GUI: The changes in properties of OR controls in a software is called behavioral or GUI.
- Input Domain: Whether the objects are taking correct type and size of inputs or not?
- Error Handling: Whether our software is preventing wrong operations or not?
- Manipulations: Whether our software is generating correct output or not?
- Database Validity: Whether our software front end screens operations are correctly impacting on database of the software or not?
- Sanitation: Finding extra operations in a software with respect to customer requirements.
The above factors checking on a software is called as functional testing. During this checking the testers are usingbox testing or closed box testing techniques.
Non-Functional Testing: After completion of functional testing successfully, the testing team is concentrating on non-functional testing. During non-functional testing, the testing team is concentrating on customer expectations or software characteristics.
This non-functional testing is classified into below sub testing topics.
- Usability Testing (UI Check)
- Check (Help documents testing)
- Compatibility Testing OR Portability Testing
- Configuration Testing
- Inter system Testing
- Multi languity Testing
- Data volume Testing
- Performance Testing
- Endurance Testing
- Security Testing
- Parallel Testing
- User Acceptance Testing (UAT)
- Software Release and Release Testing