Một số câu hỏi phỏng vấn Manual Tester (Software Testing) trong năm 2023 mà các bạn có thể tham khảo dưới đây
1. What is Software Testing?
Answer: Software testing is a process of evaluating a software application to identify defects and ensure that it meets specified requirements and functions as expected.
2. What are the objectives of Software Testing?
Answer: The objectives of software testing include finding defects, ensuring software functionality, verifying requirements, enhancing software quality, and providing confidence in the software.
3. What are the different levels of testing?
Answer: There are various levels of testing, including:
Unit Testing
Integration Testing
System Testing
User Acceptance Testing (UAT)
4. What is the purpose of Regression Testing?
Answer: Regression testing verifies that recent code changes do not negatively impact existing functionality, ensuring that new features or fixes do not introduce new defects.
5. Explain the term “Test Case”
Answer: A test case is a set of conditions, steps, and inputs that a tester executes to verify specific functionality in a software application. It includes expected results and preconditions.
6. What is the Test Plan, and why is it important?
Answer: A test plan is a document that outlines the approach, scope, objectives, resources, and schedule for testing. It’s crucial for providing a roadmap for testing activities and ensuring alignment with project goals.
7. What is a Test Scenario?
Answer: A test scenario is a high-level description of a testing situation that may consist of multiple related test cases. It outlines a specific testing condition.
8. How do you prioritize Test Cases?
Answer: Test cases can be prioritized based on factors such as business impact, critical functionality, and risk assessment. High-priority test cases should be tested first.
9. What is Smoke Testing?
Answer: Smoke testing is a quick, high-level test to determine whether the software build is stable enough for more extensive testing. It checks basic functionality and ensures the build is deployable.
10. What is Sanity Testing?
Answer: Sanity testing is a type of software testing performed after minor changes or bug fixes to ensure that the specific areas affected by the changes are still functioning correctly. It is a subset of regression testing and focuses on verifying that the recent modifications have not adversely impacted the core functionality of the software.
11. Explain the term “Defect Life Cycle”
Answer: The defect life cycle represents the stages that a defect goes through, from discovery to resolution. Common stages include New, Assigned, In Progress, Fixed, Verified, and Closed.
12. What is a Test Environment, and why is it important?
Answer: A test environment is a setup that mimics the production environment. It’s essential for testing because it ensures that software behaves as expected in real-world conditions.
13. What is Boundary Testing?
Answer: Boundary testing examines values at the edge of the input domain. It aims to find defects related to boundary conditions, such as minimum and maximum input values.
14. What is Compatibility Testing?
Answer: Compatibility testing ensures that the software functions correctly on various platforms, browsers, devices, and operating systems.
15. What is Negative Testing?
Answer: Negative testing involves intentionally providing incorrect inputs or using invalid conditions to verify that the software can handle errors gracefully.
16. Explain the term “Traceability Matrix”
Answer: A traceability matrix is a document that establishes a link between requirements and test cases. It helps ensure that all requirements are covered by test cases.
17. What is Ad-hoc Testing?
Answer: Ad-hoc testing is informal testing where testers explore the application without predefined test cases. It aims to discover defects through unscripted exploration.
18. What is Exploratory Testing?
Answer: Exploratory testing is a testing approach where testers simultaneously learn about the application while designing and executing test cases. It’s particularly useful for complex or poorly-documented systems.
Xem thêm: Kiểm thử khám phá (Exploratory Testing)
19. What is Alpha Testing and Beta Testing?
Answer: Alpha testing is performed by the development team in a controlled environment. Beta testing involves end-users testing the software in a real-world setting before the official release.
20. What is Load Testing, and why is it important?
Answer: Load testing evaluates the performance of a system under expected load conditions. It helps identify bottlenecks and assesses system scalability.
21. What is Stress Testing?
Answer: Stress testing evaluates how a system behaves under extreme conditions, often beyond normal operational limits. It helps identify system weaknesses.
22. How do you handle a situation where a critical defect is found just before a release?
Answer: In such cases, the severity and impact of the defect should be communicated to stakeholders. A decision on whether to release or delay should be made based on risk assessment.
23. Explain the term “Test Coverage”
Answer: Test coverage is a measure of how much of the application’s functionality has been tested. It helps identify areas that may require additional testing.
24. What is the purpose of a Test Execution Report?
Answer: A Test Execution Report summarizes the results of test case execution. It includes information about passed, failed, and blocked test cases.
25. What is Usability Testing?
Answer: Usability testing evaluates how user-friendly a software application is by observing real users interacting with it. It helps identify user interface issues.
26. What is meant by test coverage?
Answer: Test coverage is a quality metric to represent the amount (in percentage) of testing that has been completed. It is relevant for both functional and non-functional testing activities. This metric is used to add missing test cases.
27. What is the Entry and Exit Criteria in Software Testing?
Answer: Entry criteria define the conditions that must be met before testing can begin, while exit criteria specify when testing should be considered complete.
28. What is a Test Management Tool, and why is it used?
Answer: A test management tool helps manage and organize test cases, track test execution, and generate reports. It enhances test efficiency and visibility.
29. Explain the concept of Test Automation?
Answer: Test automation is the process of using automated scripts and testing tools to perform tests, execute test cases, and compare actual results with expected results.
30. What are the benefits and limitations of Test Automation?
Answer: Benefits include repeatability, efficiency, and reduced human error. Limitations include initial setup time, maintenance effort, and unsuitability for some types of testing.
31. What is Positive and Negative Testing?
Answer: Positive testing verifies that the system behaves as expected with valid inputs, while negative testing validates that the system handles invalid inputs or error conditions appropriately.
32. What is Test Driven Development (TDD)?
Answer: Test Driven Development is a software development methodology where tests are written before writing the actual code. It helps ensure that the code meets the required functionality.
33. What is User Acceptance Testing (UAT)?
Answer: User Acceptance Testing is the final phase of testing where end-users validate whether the software meets their business requirements and is ready for production use.
34. What is Behavior-Driven Development (BDD)?
Answer: Behavior-Driven Development, is a software development approach that extends the principles of Test-Driven Development (TDD) to include collaboration between developers, testers, and non-technical stakeholders. BDD places a strong emphasis on communication and aligning development with business goals by using natural language specifications that describe the expected behavior of the software.
35. What is Regression Testing?
Regression Testing is a full or partial selection of already executed test cases that are re-executed to ensure existing functionalities work fine.
Steps involved:
Re-testing: All of the tests in the current test suite are run again. It turns out to be both pricey and time-consuming.
Regression tests are divided into three categories: feature tests, integration tests, and end-to-end testing. Some of the tests are chosen in this step.
Prioritization of test cases: The test cases are ranked according to their business impact and important functionalities.
Xem thêm: Kiểm thử hồi quy (Regression Test)
36. What is Test Harness?
A test harness is a collection of software and test data used to put a programme unit to the test by running it under various conditions such as stress, load, and data-driven data while monitoring its behaviour and outputs.
37. Differentiate between Positive and Negative Testing
Positive Testing
Negative Testing
Positive testing ensures that your software performs as expected. The test fails if an error occurs during positive testing.
Negative testing guarantees that your app can gracefully deal with unexpected user behaviour or incorrect input.
In this testing, the tester always looks for a single set of valid data.
Testers use as much ingenuity as possible when validating the app against erroneous data.
38. What is a Critical Bug?
A critical bug is one that has the potential to affect the bulk of an application’s functioning. It indicates that a significant portion of functionality or a critical system component is utterly broken, with no way to proceed. The application cannot be delivered to end users until the critical bug has been fixed.
39. What is Test Closure?
Test Closure is a document that summarises all of the tests performed throughout the software development life cycle, as well as a full analysis of the defects fixed and errors discovered. The total number of experiments, the total number of experiments executed, the total number of flaws detected, the total number of defects settled, the total number of bugs not settled, the total number of bugs rejected, and so on are all included in this memo.
40. Explain the defect life cycle
A defect life cycle is a process by which a defect progresses through numerous stages over the course of its existence. The cycle begins when a fault is discovered and concludes when the defect is closed after it has been verified that it will not be recreated.
Vài câu hỏi phỏng vấn cho Manual Tester (Software Testing) năm 2023 | Anh Tester
41. What is the pesticide paradox? How to overcome it?
According to the pesticide paradox, if the same tests are done repeatedly, the same test cases will eventually stop finding new bugs. Developers will be especially cautious in regions where testers discovered more flaws, and they may overlookPositive and Negative Testing?
other areas. Methods for avoiding the pesticide conundrum include:
To create a completely new set of test cases to put various aspects of the software to the test.
To create new test cases and incorporate them into existing test cases.
It is possible to detect more flaws in areas where defect levels have decreased using these methods.
42. What is API testing?
API testing is a sort of software testing that entails evaluating application programming interfaces (APIs) to see if they meet functionality, reliability, performance, and security requirements. Simply put, API testing is designed to detect defects, inconsistencies, or departures from an API’s expected behaviour. Typically, applications are divided into three layers:
The user interface is also known as the presentation layer.
For business logical processing, the Business Layer or application user interface is used.
API testing is done at the most vital and important layer of software architecture, the Business Layer, for modelling and manipulating data.
43. What is System testing?
System testing is a type of testing in which the entire software is tested. System testing examines the application’s compliance with its business requirements.
44. What is Acceptance testing?
Acceptance testing is a type of testing done by a possible end-user or customer to see if the software meets the business requirements and can be used.
45. Differentiate between bug leakage and bug release
Bug Leakage – When tested software is pushed into the market and the end-user discovers defects, this is known as bug leakage. These are bugs that the testing team overlooked throughout the testing phase.
Bug Release – When a certain version of software is launched into the market with some known bugs that are expected to be fixed in later versions, this is known as a bug release. These are low-priority issues that are highlighted in the release notes when sharing with end-users.
46. What do you mean by Defect Triage?
Defect triage is a procedure in which defects are prioritised depending on a variety of characteristics such as severity, risk, and the amount of time it will take to fix the fault. The defect triage meeting brings together several stakeholders – the development team, testing team, project manager, BAs, and so on – to determine the order in which defects should be fixed.
47. What is Integration Testing? What are its types?
Integration testing is performed after unit testing. We test a group of linked modules in integration testing. Its goal is to identify faults with module interaction.
The following are the types of integration testing:
Big Bang Integration Testing — After all of the modules have been merged, big bang integration testing begins.
Top-down Integration Testing — In top-down integration, testing and integration begin at the top and work their way down.
Bottom-up Integration Testing — In bottom-up integration testing, lower-level modules are tested before moving up the hierarchy to higher-level modules.
Hybrid Integration Testing — Hybrid integration testing combines top-down and bottom-up integration testing techniques. The integration with this approach starts at the middle layer, and testing is done in both directions.
