Regression Testing:
- Regression testing is one of the black box testing techniques. Regression testing is done to validate a code change in application is not impacting the existing functionality of the software.
- Regression testing is making sure that the software works fine with a new added functionality, defect fix or any other change in software.
- In Regression testing test cases are re executed to check the previous functionality is working fine or not.
- It is performed on a newly delivered build by development team after a significant change in original functionality.
- Regression testing ensures that the software still works after changes in software.
When To Perform Regression Testing:
•Regression testing is done whenever the software code is modified.
•The software code is modified in the following scenarios:
- When new functionality added to the application.
- When there is a Change Requirement.
- When there is a defect fixed.
- When there is a performance issue fix.
- When there is an environment change.
Smoke Testing :
Smoke testing is done at the time of receiving build from the development team.
- Purpose of smoke testing is to determine that the build received is testable or not.
- Smoke testing is also known as Day 0.
- Smoke testing is a time saving process. It reduces time of testing, because testing activity will only be performed when the key functionality of software are working fine.
- The main focus of smoke testing is on the working of core or primary functionality of software.
- The existing test cases are used in smoke testing. The cases are picked as per the requirement of the smoke testing.
Sanity Testing:
- Sanity testing is done at the time of build with minor changes in the functionality.
- The motive of sanity testing is to ensure that all the defects have been fixed and no defect arise from the fixed defects.
- Sanity testing is a kind of regression testing with focus on impacted modules only.
- Sanity testing make sure that changes in code or software have no impact on the connected modules. Therefore the related modules are tested in sanity testing.
- The sanity test cases are picked from test suite and no new cases are designed for sanity testing.
Exploratory Testing :
- Exploratory testing is performed in scenario when the requirements of the software are not present.
- In Exploratory testing the software is explored by testing person in every possible way. Tester understands the flow, a test document is prepared and then software is tested.
- Exploratory testing is done in following cases:
- When the requirements are missing from client.
- Early cycle of testing is required.
- The main tester of testing team are busy in critical work, and new testers joined the team.
Adhoc Testing :
- Adhoc testing is performed by checking the software or application randomly.
- Adhoc testing is also known as Monkey testing or Gorilla testing.
- Adhoc Testing is negative testing because the application is tested against the client requirements.
- When the application is tested randomly, the bugs may be noticed that can not be identified during the systematic testing cycle.
