System Testing

System Testing is the software testing to integrate whole system and verify the functionality of the system with the specified requirement. This is the Black Box testing so no knowledge regarding code is required. This is End to End Testing.

System testing basically to exercise of whole system when all interfaces combined with each other. In System Testing we check the behavior of the complete and fully integrated software product based on the requirement. System testing usually carried out by the Team which is independent of the Development Team to work with new mind for finding new bugs.



System Testing is done after the Integration Testing. System Testing test the Functional and Non Functional Requirement of the software.

Following are the System Testing Type

• Graphical User Interface Testing: In GUI Testing, we verify the user interface of the software and to check this user interface with the specified requirement. User interface means the color, font, font size, Text format, Text Box, Radio Button, Checkbox, Buttons, icons, alignment, links , pop up , contents, Menu bar, Dialog bar,  Tool bar and so many.

• Functional Testing: Functional Testing is a Quality Assurance process in which, QA team provide the input to the function and check the output without checking the internal structure of the function. This is a Black Box Testing. In the Function Testing, Test team provide the input and check the output to validate that whether the output matching with the expected output.

• Usability Testing: In Usability Testing, we verify that the system should be easy to use for the end users. The Main Focus in this testing to make software easy to use, flexible, attractive, easy to operate, easy to learn, fast and system should meet it's objective. Usability Testing done with end user perspective.

• Performance Testing: Performance Testing is the testing in which Test Team determine how the system will perform in terms of responsiveness and when the system will be overloaded. In Performance Testing , we validate or verify the scalability, reliability and how the system uses the available resources. These all are the quality attribute of the system.

• Compatibility Testing: Compatibility Testing is the software non functional testing in which we check the relationship of the software with the computing environment. In Compatibility Testing, One can verify that how your software is working with the Operating Systems, Other Hardwares, Network and other devices.

• Load Testing: Meaning of Load Testing is to provide constantly or steadily  load for a software to check that how software is responding in increasing load without significant performance degradation. Load Testing is put load over the system to check the response. We increase the limit until the threshold limit. In Load Testing we determine the system limit in normal load and peak load limit of the system.

• Volume Testing: In this type of Testing, We put the huge load for the limited time to check the behavior of the Application. Suppose you want the Volume Test then you need to increase the size of the database so that it can accept the heavy load so in this testing we check the performance of database with increasing volume.

• Stress Testing: Stress Testing is the testing to verify the response/output of the software beyond the breaking point of the system.  Stress Testing, test team focus on robustness, availability and the error handling under the heavy load rather then correct behavior under normal circumstances. It is the type of non functional testing.

• Security Testing
• Scalability Testing: Scalability Testing is the non functional Testing. In this Testing we check the capability of the system in scale up or scale down. Scale Up and Scale down to means to check the capability of the system or Network to check the growing amount of work in order to accommodate that growth. In Scalability Testing we measure the system capability in terms of growing the workload per user, Growing the concurrent users or the size of the database.

• Smoke Testing: In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.

• Sanity Testing: Sanity Testing is perform when QA team received the build after fixes of minor bugs or some new functionality added. In Sanity Testing, QA team check that the bugs that generated in last build should be fix and due to those bug fixes there should be no new bugs generated. So in Sanity Testing first QA team check the regression testing and after regression testing QA team verify the previous bugs.

• Exploratory Testing
• Ad Hoc Testing
• Regression Testing
• Installation Testing
• Maintenance Testing
• Recovery Testing