Questions Manual Testing
1. What is manual testing?
2. What is the difference between manual testing and automated testing?
3. What are the different levels of testing?
4. What is a test case?
5. What is a bug? How do you report it?
6. What is regression testing?
7. What is the difference between severity and priority?
8. What are the different types of testing?
9. What is a test plan?
10. What are the steps involved in the Software Testing Life Cycle (STLC)?
11. What is exploratory testing?
12. How do you ensure test coverage?
13. What is boundary value analysis?
14. What is equivalence partitioning?
15. What is alpha testing?
16. What is beta testing?
17. What are some common challenges faced in manual testing?
18. What is a smoke test?
19. What is a sanity test?
20. What is the role of documentation in manual testing?
21. How do you prioritize testing tasks?
22. What is a test suite?
23. What is user acceptance testing (UAT)?
24. What are some common bug tracking tools?
25. How do you define 'done' for a testing phase?
Software Testing (Manual/Automation) Interview Questions
Are you preparing for a Software Testing interview? Here are 25 (Manual/Automation) essential questions to help you succeed in your interview and demonstrate your mastery of Scrum.
Top Manual Testing Interview Questions & Answers
1. What is manual testing?
- Manual testing is the process of manually checking software for defects by executing test cases without the use of automation tools.
- It involves evaluating the application’s behavior and user interface to ensure it meets requirements.
2. What is the difference between manual testing and automated testing?
- Manual testing requires human intervention to execute test cases, making it suitable for exploratory and usability testing.
- Automated testing uses scripts and tools to execute tests automatically, which is efficient for repetitive tasks and regression testing.
3. What are the different levels of testing?
- Unit Testing: Tests individual components.
- Integration Testing: Tests interactions between integrated components.
- System Testing: Tests the entire system as a whole.
- Acceptance Testing: Validates the system against business requirements.
4. What is a test case?
- A test case is a documented set of conditions and variables under which a tester determines whether a system behaves as expected.
- It typically includes test case ID, description, preconditions, steps to execute, and expected results.
5. What is a bug? How do you report it?
- A bug is an error or flaw in software that produces incorrect or unexpected results.
- To report it, you typically include a bug ID, summary, steps to reproduce, expected and actual results, and severity/priority levels.
6. What is regression testing?
- Regression testing involves retesting the application after changes (like bug fixes or new features) to ensure that existing functionalities remain unaffected.
7. What is the difference between severity and priority?
- Severity refers to the impact of a bug on the application's functionality, while priority indicates how quickly a bug should be fixed based on business needs.
8. What are the different types of testing?
- Functional Testing: Validates functionalities against requirements.
- Non-Functional Testing: Evaluates performance, usability, and security.
- Smoke Testing: Quick checks of critical functionalities.
- User Acceptance Testing (UAT): Conducted by end-users to ensure the software meets their needs.
9. What is a test plan?
- A test plan is a document outlining the testing strategy, scope, resources, schedule, and activities for a project, serving as a roadmap for the testing process.
10. What are the steps involved in the Software Testing Life Cycle (STLC)?
- Requirement analysis
- Test planning
- Test case design
- Test environment setup
- Test execution
- Defect reporting
- Test closure activities
11. What is exploratory testing?
- Exploratory testing is an informal testing approach where testers explore the application without predefined test cases, using their intuition and experience to identify defects.
12. How do you ensure test coverage?
- Test coverage is ensured by creating comprehensive test cases that cover all functional requirements, performing traceability analysis, and using testing techniques like boundary value analysis.
13. What is boundary value analysis?
- Boundary value analysis is a testing technique that focuses on testing at the boundaries between equivalence classes.
- It involves checking values at, just above, and just below the boundaries.
14. What is equivalence partitioning?
- Equivalence partitioning divides input data into valid and invalid partitions to minimize the number of test cases while ensuring adequate coverage by testing one representative value from each partition.
15. What is alpha testing?
- Alpha testing is a type of acceptance testing performed by internal teams before releasing the software to external users, aimed at identifying bugs and gathering feedback.
16. What is beta testing?
- Beta testing is a type of acceptance testing performed by external users in a real-world environment to gather feedback and identify any remaining defects before the official product launch.
17. What are some common challenges faced in manual testing?
- Common challenges include managing tight deadlines, handling frequent requirement changes, maintaining documentation, and dealing with complex applications.
18. What is a smoke test?
- A smoke test is a preliminary test to check the basic functionality of an application after a build, ensuring that critical features work before more detailed testing.
19. What is a sanity test?
- A sanity test is a focused test conducted to verify that specific functionality or bug fixes work as expected after changes, ensuring the application is stable for further testing.
20. What is the role of documentation in manual testing?
- Documentation is crucial for providing references for test cases, ensuring consistent testing practices, facilitating communication, and recording testing outcomes and defect reports.
21. How do you prioritize testing tasks?
- Testing tasks are prioritized based on business impact, risk assessment, complexity, and feedback from customers or stakeholders.
22. What is a test suite?
- A test suite is a collection of test cases that are intended to be executed together, helping organize and manage tests related to specific functionalities or modules.
23. What is user acceptance testing (UAT)?
- UAT is the final testing phase where end-users validate the software against their requirements and ensure it meets their expectations before the product is released.
24. What are some common bug tracking tools?
- Common bug tracking tools include JIRA, Bugzilla, Mantis, Trello, and Redmine, which help in tracking and managing bugs and issues.
25. How do you define 'done' for a testing phase?
- A testing phase is considered 'done' when all planned test cases are executed, all critical bugs are resolved, and the application meets the defined acceptance criteria and quality standards.
