Briefly about System Testing
The procedure of system checking is connected with unit, integration and acceptance testing. System testing is conducted in order to check functional and nonfunctional requirements to the system as a unique entity. A huge number of system errors can be detected during this software testing type.
Thus, there is a high possibility of various risks connected with the system behavior under different conditions and environments. To minimize these risk, it is necessary to perform the checking procedure of the system in the close-to-real environment – one in which the product is going to be installed after its final release.
What errors May be detected during system testing?
- Improper usage of system capacities
- Unspecified data combinations of the user’s level
- Incompatibility to the environment.
- Unexpected use cases
- Low usability
- Improper functional or its absence, etc.
There are two approaches to system testing:
- requirements based,
- use case based.
According to the first approach, the test cases are designed for every requirement point to check it. On the basis of usage scenarios, the use cases are created. One or several scenarios may be defined for a particular use case. Every checking of each scenarios requires test cases that should be tested.
Imagine that system testing is like the process of car manufacturing. Firstly, every detail is created and checked separately (unit testing). Then the specialists check car color, engine after 2,000 miles, wheels after some more distance, electronics and so on. Every functional aspect is checked. The same with software products. It is necessary cover as much of system aspects as possible to provide a full test coverage.
Learn more from QATestLab
Related Posts:
About Article Author
view more articles
No Comments Yet!
You can be the one to start a conversation.