30+ Software Manual Tester Interview Questions and Answers

The next phase after Test Implementation in STLC is Test Execution, where test cases are executed and results are recorded.

• Test Execution involves running the test cases as per the test plan.

• Defects are logged if the actual results do not match the expected results.

• Example: Running a regression test suite after a new feature is added.

• Test Execution can be manual or automated, depending on the test strategy.

• Results are documented for further analysis and reporting.

Re-testing is necessary to ensure that the fixes made during regression testing have resolved the identified defects.

• Re-testing helps validate that the defects identified during regression testing have been fixed.

• Regression testing focuses on ensuring that existing functionality is not affected by new changes.

• Re-testing focuses on verifying that the specific defects have been resolved.

• Regression testing may not cover all the scenarios or combinations that caused the defects i...read more

After Test Planning, the next steps in STLC include Test Execution, Defect Reporting, and Test Closure.

• Test Execution: Execute the test cases in the test environment. For example, running a login test case to verify user authentication.

• Defect Reporting: Log any defects found during testing in a defect tracking tool. For instance, reporting a bug when a user cannot log in.

• Test Closure: Evaluate cycle completion, prepare test closure report, and gather lessons learned. This may...read more

Testing is typically performed after development activity.

• Testing is usually done after the development of the software to ensure that the product meets the requirements and functions correctly.

• Testing before development is not practical as there would be no software to test.

• Testing after development allows for identifying and fixing any issues or bugs before the software is released to users.

Authentication is the process of verifying the identity of a user, while authorization is the process of granting access to specific resources.

• Authentication confirms the identity of a user through credentials such as username and password.

• Authorization determines what resources a user can access based on their role or permissions.

• Authentication and authorization are crucial for ensuring the security of software systems.

• Examples of authentication and authorization include log...read more

Retest is the process of testing a previously failed test case again after the defects have been fixed. Test Load refers to the amount of work that a system can handle.

• Retest is done to ensure that the defect has been fixed and the system is working as expected.

• Test Load testing is done to determine the maximum capacity of the system and to identify any performance issues.

• Retest is a part of regression testing while Test Load testing is a part of performance testing.

• Example o...read more

Smoke testing is a quick test to check if the software build is stable, while regression testing is a comprehensive test to ensure new changes do not affect existing functionality.

• Smoke testing is done to check if the critical functionalities of the software are working fine after a build, while regression testing is done to ensure that new changes do not impact existing functionalities.

• Smoke testing is a subset of regression testing and is usually done before regression test...read more

Testing is typically conducted after development, but can also occur in parallel to ensure quality and catch issues early.

• Testing after development allows for a complete product to be evaluated, ensuring all features work as intended.

• Example: A web application is fully developed, then undergoes functional testing to verify user interactions.

• Testing before development (like in Test-Driven Development) ensures that requirements are clear and helps guide the coding process.

• Examp...read more

Agile model is a software development approach where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.

• Iterative and incremental development

• Customer involvement and feedback

• Adaptive planning and flexibility

• Cross-functional teams working in short cycles called sprints

• Continuous integration and testing

Prioritize requirements based on risk, impact, and complexity to optimize testing time and ensure critical functionalities are validated first.

• Focus on high-risk requirements that could lead to significant issues if not tested, e.g., payment processing in an e-commerce app.

• Prioritize requirements that impact core functionalities, such as user authentication in a banking application.

• Consider dependencies; test requirements that other features rely on first, like a database con...read more

A bug is an issue or defect in a software application that causes it to not work as intended.

• Bugs can range from minor issues like typos to major problems like crashes or data loss

• Examples of bugs include incorrect calculations in a financial application, broken links on a website, or a login form not working properly

Positive testing is validating that the system works as expected with valid inputs, while negative testing is testing the system with invalid inputs to ensure it handles errors correctly.

• Positive testing involves testing the system with valid inputs to ensure it produces the expected results.

• Negative testing involves testing the system with invalid inputs to ensure it handles errors gracefully.

• Examples of positive testing include entering a valid email address in a login form...read more

Regression testing is testing the entire application after changes, while retesting is testing a specific bug fix.

• Regression testing ensures that new code changes do not affect existing functionality

• Retesting focuses on verifying that a specific bug fix has been successfully implemented

• Regression testing is done after every code change, retesting is done after a bug fix

• Regression testing involves running a full suite of tests, retesting focuses on the specific test case relat...read more

Test case scenario is a detailed description of a specific test case that includes input data, expected output, and steps to be followed.

• Test case scenario is a set of steps that a tester follows to validate a particular functionality of the software.

• It includes input data, expected output, and steps to be followed.

• Test case scenarios are designed to ensure that the software meets the requirements and specifications.

• They help in identifying defects and ensuring that the softw...read more

Load testing checks system performance under normal and peak loads, while stress testing checks system performance beyond peak loads.

• Load testing checks system performance under normal and peak loads

• Stress testing checks system performance beyond peak loads

• Load testing is used to identify bottlenecks and optimize system performance

• Stress testing is used to identify system failure points and determine system capacity

• Load testing is typically performed over a longer period of t...read more

Test Strategy is a high-level plan to achieve testing objectives and goals.

• It outlines the testing approach, scope, and objectives.

• It defines the testing methods, techniques, and tools to be used.

• It identifies the roles and responsibilities of the testing team.

• It includes the test environment, test data, and test schedule.

• It is created based on project requirements and risks.

• Example: A test strategy for a web application may include functional, performance, security, and usab...read more

Test cases can be solved by analyzing requirements, designing test scenarios, executing tests, and reporting defects.

• Understand the requirements thoroughly

• Design test scenarios based on requirements

• Execute test cases using test data

• Report defects found during testing

• Retest fixed defects to ensure they are resolved

Black box testing is a software testing method where the internal structure or code of the application is not known to the tester.

• Tester focuses on the functionality of the software without knowing its internal workings

• Tests are based on requirements and specifications

• Input data is provided and output is compared with expected results

• Examples: equivalence partitioning, boundary value analysis

Understanding software development involves grasping methodologies, tools, and processes for creating quality software products.

• Software Development Life Cycle (SDLC) includes phases like planning, design, development, testing, deployment, and maintenance.

• Agile methodology emphasizes iterative development and collaboration, allowing for flexibility and faster delivery of software.

• Version control systems like Git help manage changes to code, enabling collaboration among multip...read more

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 application

• 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 additions, and software upgrades

Manual testing techniques are methods used to test software manually without the use of automation tools.

• Black box testing

• White box testing

• Grey box testing

• Ad-hoc testing

• Exploratory testing

• Regression testing

• Boundary value analysis

• Equivalence partitioning

• Error guessing

• Usability testing

Software Testing Life Cycle is a process of testing software from planning to deployment.

• STLC consists of 6 phases: Requirement Analysis, Test Planning, Test Case Development, Test Environment Setup, Test Execution, and Test Closure.

• Each phase has its own set of activities and deliverables.

• STLC ensures that the software meets the quality standards and is free from defects.

• It helps in identifying defects early in the development cycle, reducing the cost of fixing them later.

• ST...read more

Test case for login page

• Verify login with valid credentials

• Verify login with invalid credentials

• Verify login with empty username and password fields

• Verify login with only username field filled

• Verify login with only password field filled

• Verify login with special characters in username and password fields

Test data is the input or set of inputs used to test a software application.

• Test data can be both valid and invalid inputs.

• It is used to verify the functionality, performance, and reliability of the software.

• Examples of test data include usernames, passwords, numbers, dates, and special characters.

Testing is a process of finding defects while QA is a process of preventing defects.

• Testing is reactive while QA is proactive.

• Testing is focused on finding errors while QA is focused on preventing them.

• Testing is a subset of QA.

• QA involves processes and procedures while testing involves executing tests.

• QA is a continuous process while testing is a one-time activity.

STLC (Software Testing Life Cycle) consists of various phases to ensure quality software delivery.

• 1. Requirement Analysis: Understand the project requirements.

• 2. Test Planning: Define test objectives, scope, and strategy.

• 3. Test Design: Create test cases and test data.

• 4. Test Execution: Run test cases and report defects.

• 5. Defect Tracking: Log and track defects until resolution.

• 6. Test Closure: Evaluate test results and prepare test closure report.

Test scenarios for login functionality

• Verify valid username and password login successfully

• Verify error message displayed for invalid username or password

• Verify user is redirected to forgot password page when clicking on forgot password link