Great job on starting a new lesson! After reading this lesson, click Next 👉 button at bottom right to continue to the next lesson.
System testing is a a test level in software testing that evaluates the overall functionality and other quality attributes of your integrated software. It tests if the system meets the specified requirements and design. In system testing, you find out if the system is ready for user acceptance testing by the end-users. System testing is performed after integration testing and before user acceptance testing.
System testing examples
- Functional testing: It tests the functionalities and features of the software. For example, testing the login functionality of a web application, or testing the website reports.
- Performance testing: It tests the speed, scalability, stability and reliability of the software. For example, simulating multiple users on a mobile application and measuring it's response time, throughput, and resource utilization.
- Security testing: It tests the security of the software against various threats and attacks. For example, testing that the input fields do not accept code, or testing that the payment transactions are encrypted and secure.
- Usability testing: It tests the user-friendliness and ease of use of the software. For example, testing that the user interface is intuitive and the work flow is logical.
Tips for System Testing
- Create tests that cover all the functional and non-functional requirements, technical specifications and quality standards.
- Use the test environment that is exactly or very similar to the real-time production environment.
- Use the standard tools in your project test automation, user simulation, monitoring, etc.
- After defect fixes or other changes to the test environment, perform regression testing to check for unwanted effects of the changes.
- Report defects promptly.
FAQ (interview questions and answers)
- What is the difference between system testing and integration testing?
System testing tests the functionality and other qualities (such as performance and security) of your entire software as a single system, while integration testing tests the interactions, between individual components or modules of your software. System testing follows successful integration testing. - What are some of the types of system testing?
Functional testing, performance testing, security testing, compatibility testing, and usability testing. - What is the primary purpose of system testing?
Evaluate the integrated system against the specified requirements and design. - Who owns system testing?
The testers, who are not developers. These testers should have a good knowledge of the system requirements and design specifications, and the tools for test automation and monitoring the system.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.