Akiko Sherman Infotech Softwaretest Engineer Interview Questions, Process, and Tips

Regression testing is the process of testing changes made to a software application to ensure that existing functionality still works.

• It is performed after making changes to the software

• It ensures that existing functionality is not affected by the changes

• It helps to identify any new defects introduced by the changes

• It can be automated to save time and effort

• Examples include testing after bug fixes, new feature addition

Smoke testing is a preliminary testing technique to check if the critical functionalities of the software are working fine.

• It is a quick and shallow testing technique

• It is performed to ensure that the build is stable enough for further testing

• It is usually performed after every build

• It helps in identifying critical defects early in the testing cycle

• Example: Testing the login functionality of a website after a new build

Sanity testing is a quick and shallow testing technique to ensure that the application is stable enough for further testing.

• It is performed after every build to check if the critical functionalities are working as expected.

• It is a subset of regression testing.

• It is not a replacement for thorough testing.

• It helps to save time and effort by identifying major issues early in the testing process.

• Example: Checking if the lo

Retesting is testing the same functionality again after fixing the defects. Regression testing is testing the unchanged functionality to ensure that it still works after changes.

• Retesting is done to ensure that the defects reported in the previous cycle have been fixed.

• Regression testing is done to ensure that the changes made to the software have not affected the existing functionality.

• Retesting is done on the same te...read more

Black box testing is a software testing technique where the internal workings of the system are not known to the tester.

• Tests are performed based on the system's inputs and outputs

• The tester does not have access to the source code or internal structure of the system

• It focuses on the functionality of the system rather than its implementation

• Examples include user acceptance testing, regression testing, and integration te