System testing is testing the application as a whole that is testing both the hardware and software requirements in a complete integrated system or testing the complete product. System testing can be of black box testing since the tester need not have any knowledge on the internal code structure. It is a series of tests carried out to perform full testing of a product. It is also called as end to end testing. We will look for some of the types of testing included in system testing
1. Performance testingTesting the performance of the application to determine how it works on heavy load in terms of responsiveness and stability.
2. Load testing
Testing the behavior of the application under a normal load. During peak hours the server and the database will be monitored to find out the response time. Mostly this type of testing will be automated.
3. Stress Testing
1. Performance testingTesting the performance of the application to determine how it works on heavy load in terms of responsiveness and stability.
2. Load testing
Testing the behavior of the application under a normal load. During peak hours the server and the database will be monitored to find out the response time. Mostly this type of testing will be automated.
3. Stress Testing
This type of testing is carried out to find the breakpoint of the application. The tolerated amount of load that the application can accept. Testing the behavior of the application under a extreme load.
4. Endurance TestingThroughput and response time are monitored with continuous load to the application. Application will be tested continuously for 48 or 72 hours to determine the system behavior.
5. Spike testing
Increasing the load suddenly at a specified amount of time to determine the behavior of the application.
6. Compatibility testingTesting the application to determine the compatibility like whether the application runs on multiple host, supports different platforms (OS), Compilers.
7. GUI Testing
Graphical User Interface Testing. This testing should be carried out manually. We will test mainly for the user friendliness of the application. Will check for the icons, look & feel, easy drag & drop, table selection, color of the screens.
8. Usability Testing
Testing the whole product to determine whether the product developed satisfies the intended purpose and is of easy to use for the end users (customers).
9. Regression Testing
Testing the application once the developers has given the fixes for the bugs raised or once the requirements have been changed. The purpose of this testing is to ensure that no old bugs reappear and fixing of bugs should not have caused new bugs during development process.
4. Endurance TestingThroughput and response time are monitored with continuous load to the application. Application will be tested continuously for 48 or 72 hours to determine the system behavior.
5. Spike testing
Increasing the load suddenly at a specified amount of time to determine the behavior of the application.
6. Compatibility testingTesting the application to determine the compatibility like whether the application runs on multiple host, supports different platforms (OS), Compilers.
7. GUI Testing
Graphical User Interface Testing. This testing should be carried out manually. We will test mainly for the user friendliness of the application. Will check for the icons, look & feel, easy drag & drop, table selection, color of the screens.
8. Usability Testing
Testing the whole product to determine whether the product developed satisfies the intended purpose and is of easy to use for the end users (customers).
9. Regression Testing
Testing the application once the developers has given the fixes for the bugs raised or once the requirements have been changed. The purpose of this testing is to ensure that no old bugs reappear and fixing of bugs should not have caused new bugs during development process.
Posts
{ 0 comments... read them below or add one }
Post a Comment