1. What is Software Testing? Software testing is the process of evaluating and verifying that a software application or system meets specified requirements. It aims to identify defects, ensure quality, and improve performance. 2. What are the different levels of testing? The main levels of testing are: Unit Testing Integration Testing System Testing Acceptance Testing 3. What is the difference between verification and validation? Verification: Ensures the product is built correctly by checking it meets specifications (Are we building the product right?). Validation: Ensures the product meets the user’s needs and requirements (Are we building the right product?). 4. What is a Test Case? A test case is a set of conditions or variables under which a tester determines whether a software system is working correctly. 5. What is Test Coverage? Test coverage is a metric used to measure the amount of testing performed by a set of tests, often represented as the percentage of code, requirements, or functionality tested. 6. What is a Test Plan? A test plan is a document that outlines the strategy, scope, objectives, resources, schedule, and activities to be executed during the testing process.
7. What is the V-Model in software testing? The V-Model is a development model that emphasizes verification and validation by corresponding each development phase with a testing phase. 8. What are the different types of testing? Functional Testing Non-Functional Testing Regression Testing Usability Testing Performance Testing Load Testing Stress Testing Security Testing 9. What is the difference between a bug, defect, and error? Error: A mistake made by a developer. Defect: A flaw in software, identified during testing. Bug: A defect found in production or during testing. 10. What is boundary value analysis? Boundary value analysis is a testing technique where test cases are designed based on boundary values (extreme values at the limits of input). 11. What is equivalence partitioning? Equivalence partitioning divides input data into equivalent partitions so that test cases can cover each partition, reducing the number of test cases.
12. What is a use case? A use case describes the interactions between a user and the system to achieve a specific goal, often used to derive test cases. 13. What is a test environment? A test environment is the combination of hardware, software, and network configuration where testing is executed. 14. What is a defect life cycle? The defect life cycle represents the stages a defect goes through from identification to closure, including states like New, Assigned, Fixed, and Closed. 15. What is regression testing? Regression testing is performed to ensure that new changes or updates to the code do not negatively affect the existing functionality. 16. What is retesting? Retesting is the process of testing a failed test case again after defects have been fixed. 17. What is a Test Summary Report? A test summary report provides a summary of testing activities and results, typically presented at the end of a testing cycle. 18. What is a bug severity? Bug severity refers to the impact a defect has on the system, such as Critical, Major, Minor, or Trivial.
19. What is the difference between functional and non- functional testing? Functional Testing: Validates the system against functional requirements. Non-Functional Testing: Validates system performance, usability, reliability, etc. 20. What is performance testing? Performance testing assesses the speed, responsiveness, and stability of a system under a workload. 21. What is load testing? Load testing determines how the system behaves under expected user loads. 22. What is stress testing? Stress testing evaluates how the system behaves under extreme or unexpected workloads, testing its limits. 23. What is acceptance testing? Acceptance testing ensures that the system meets business requirements and is ready for release, often performed by end users. 24. What is smoke testing? Smoke testing is a preliminary test to check the basic functionality of the software build. 25. What is sanity testing? Sanity testing verifies that specific functionalities are working after minor changes in the code.
26. What is black-box testing? Black-box testing is a testing technique where the tester doesn't need to know the internal code structure, focusing only on inputs and outputs 27. What is white-box testing? White-box testing involves testing internal structures or workings of an application, requiring knowledge of the code 28. What is grey-box testing? Grey-box testing is a combination of both black-box and white-box testing, where testers have partial knowledge of the internal structure. 29. What is a test data? Test data is data that is used to test the functionality of the software, including positive and negative inputs. 30. What is test execution? Test execution is the process of running the tests and comparing the expected results with actual results 31. What is the role of a QA in software development? QA ensures the software meets quality standards through planning, monitoring, and managing the testing process. 32. What is static testing? Static testing involves reviewing and inspecting the code, requirements, or design without executing the program 33. What is dynamic testing? Dynamic testing involves executing the software and verifying the output against expected results.
34. What is exploratory testing? Exploratory testing is an informal, ad-hoc testing method where testers actively explore the application while testing, without predefined test cases. 35. What is a test script? A test script is a set of instructions to be followed during the testing process, detailing the steps, inputs, and expected outcomes. 36. What is alpha testing? Alpha testing is done internally by the development team before releasing the software to external users. 37. What is beta testing? Beta testing is performed by a select group of external users in a real-world environment before the final release. 38. What is a test strategy? A test strategy is a high-level document that outlines the testing approach, including objectives, resources, scope, and methods. 39. What is defect priority? Defect priority defines the order in which a defect should be fixed, often based on business needs or impact. 40. What is test-driven development (TDD)? TDD is a software development approach where test cases are written before writing the code, ensuring code meets test requirements. 41. What is defect tracking? Defect tracking involves recording, managing, and monitoring defects in a system to ensure they are resolved.
42. What is a test closure activity? Test closure activities include finalizing test reports, documenting lessons learned, and archiving test artifacts once testing is complete. 43. What are entry and exit criteria? Entry Criteria: Conditions that must be met before testing begins. Exit Criteria: Conditions that must be met before testing can be concluded. 44. What is risk-based testing? Risk-based testing focuses on testing the most critical areas of the application that are prone to defects or have a high impact. 45. What is usability testing? Usability testing evaluates how easy and user-friendly the software is by observing real users interact with the system. 46. What is root cause analysis in testing? Root cause analysis identifies the underlying cause of defects in order to prevent recurrence. 47. What is defect triage? Defect triage is the process of reviewing, prioritizing, and assigning defects for resolution based on severity and impact. 48. What is test effort estimation? Test effort estimation is the process of estimating the time and resources required for testing activities.
49. What are test metrics? Test metrics are quantitative measures used to evaluate the progress, quality, and effectiveness of the testing process. 50. What is the role of a Test Manager? A Test Manager oversees the entire testing process, ensuring the planning, execution, and closure of testing activities align with project goals.