Showing posts with label Levels of testing. Show all posts
Showing posts with label Levels of testing. Show all posts

Sunday, 13 September 2015

System Testing

System Testing is a crucial level of testing in which once the entire application is developed it is deployed into the system test environment. It is considered as full pledge testing which includes or covers both functional testing and non-functional testing such as GUI testing, load testing, stress testing, performance testing, security testing etc.
System testing is a black box testing technique and is always done by testing engineers or QA’s. During System Testing phase testing team will be involved to perform testing on the application by executing the test cases considering the entire application as single unit.
Entry Criteria for System testing:
An integration testing of modules should be completed successfully and all the defects encountered should be closed.
Exit criteria for System testing:
All planned test cases should be executed and all encountered defects should be closed.After successful completion of System testing the technical team will deploy the same piece of code into UAT environment.

system testing
System Testing
 Example of System testing:
Testing of online banks internet banking portal which includes various modules like login, balance inquiry, statement inquiry etc and integration modules like call to third party transfer screen, payment gateway etc as single unit.

Monday, 22 June 2015

Unit Testing

Testing the smallest piece of testable module/unit/software is called Unit testing. As Unit testing requires coding knowledge, normally it is done by developers.
The objective of unit testing is to test smallest piece of testable software in the product or application and separate it from the remainder of the code to determine whether it is behaving exactly as expected or not.
Each unit of code is tested in isolated fashion and then it is integrated into the module to test the module interfaces. Unit testing has proven its value in finding a large percentage of defects during use.
Drivers and stubs are written for unit testing. The driver simulates a calling unit and the stub simulates a called unit. Finding errors in isolated module is much cheaper than in complex integrated module.
E.g. Testing a banking website consists of testing the Login functionality, page submits functionality, and page navigation functionality in isolated fashion is few possible scenarios of unit testing.
module testing_component testing
Unit Testing