Quality Assurance Manual Tester Interview Questions and Answers

SDLC, API testing, and smoke testing explained.

• SDLC is a process followed to develop software from planning to deployment.

• API testing involves checking the functionality, reliability, performance, and security of APIs.

• Smoke testing is a preliminary testing to ensure that the critical functionalities of the software are working as expected.

• API testing includes checking the response time, error codes, and data accuracy.

• Smoke testing involves testing the basic functionalities of...read more

Adhoc testing is unplanned and unstructured testing, while monkey testing is random and exploratory testing.

• Adhoc testing is performed without any specific test cases or plan.

• Monkey testing involves randomly clicking around the application to find bugs.

• Adhoc testing is more focused on exploring the application in an unplanned manner.

• Monkey testing is more about randomly interacting with the application to see how it behaves.

• Adhoc testing is usually done by experienced testers...read more

Sainty testing is a type of software testing that focuses on ensuring the system behaves correctly under extreme conditions.

• Sainty testing involves testing the system with maximum and minimum values of input data.

• It also includes testing the system with high loads, stress, and peak usage scenarios.

• The goal of sainty testing is to identify any potential issues or failures when the system is pushed to its limits.

• Examples of sainty testing include testing a website with a high n...read more

Software Test Life Cycle (STLC) is a sequence of activities performed to ensure quality in software testing.

• STLC includes planning, designing, executing, and reporting phases.

• It starts with requirement analysis and ends with closure.

• STLC ensures that the software meets the specified requirements and is free from defects.

• It involves creating test cases, executing them, and reporting defects.

• STLC is an iterative process and may involve retesting and regression testing.

High and low priority are used to determine the urgency of fixing a defect or implementing a feature.

• High priority issues are critical and must be fixed immediately, such as a system crash or security vulnerability.

• Low priority issues are less urgent and can be addressed later, such as minor UI improvements or non-critical functionality.

• Priority is often determined by the impact on the user or business, as well as the effort required to fix or implement.

• Priority can be assign...read more