Here are some manual testing interview questions and answers.
You can also check out some articles on
Bug Life Cycle.
1. What are Verification and Validation?
– Verification: The process of evaluating software to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase.
– Verification is ensuring that the product has been built according to the requirements and design specifications.
– Validation: The process of evaluating software during or at the end of the development process to determine whether it satisfies specified requirements.
– Validation ensures that the product actually meets the user’s needs and that the specifications were correct.
2. What is the difference between a test plan and a QA plan?
A test plan tells what needs to be done to test the product and includes how quality control will work to identify errors and defects. On the other hand, a QA plan is more concerned with the prevention of errors and defects rather than testing and fixing them.
3. How to test an application if the requirements are not available?
If requirements documentation is not available for an application, a test plan can be written based on assumptions made about the application. Assumptions that are made should be well documented in the test plan.
4. What is a peer review?
Peer reviews are reviews conducted among people who are working in the same team. For example, a test case that was written by one QA engineer may be reviewed by a developer and/or another QA engineer.
5. Give an example of what can be done when a bug is found.
When a bug is found, it is a good idea to run more tests to be sure that the problem witnessed can be clearly detailed. For example, let say a test case fails when Animal=Cat and. A tester should run more tests to be sure that the same problem doesn’t exist with Animal=dog. Once the tester is sure of the full scope of the bug can be documented and the bug adequately reported.
6. Who writes test plans and test cases?
Generally, test plans are typically written by the quality assurance lead while testers usually write test cases.
7. Is quality assurance and testing the same?
Quality assurance and testing are not the same. Testing is considered to be a subset of QA. QA is should be incorporated throughout the software development life cycle while testing is the phase that occurs after the coding phase.
8. What is a negative test case?
Negative test cases are created based on the idea of testing in a destructive manner. For example, testing what will happen if inappropriate inputs are entered into the application.
9. What are the functional testing types?
The following are the types of functional testing:
10. What is random testing?
Random testing involves checking how the application handles input data that is generated at random. Data types are typically ignored and a random sequence of letter, numbers, and other characters are inputted into the data field.
11. What is the difference between Quality Control and Quality Assurance?
Quality control (QC) and quality assurance (QA) are closely linked but are very different concepts. While QC evaluates a developed product, the purpose of QA is to ensure that the development process is at a level that makes certain that the system or application will meet the requirements.
12. What is the difference between regression testing and retesting?
Regression testing is performing tests to ensure that modifications to a module or system do not have a negative effect on previous releases. Retesting is merely running the same testing again. Regression testing is widely asked manual testing interview questions and hence further research to understand this topic is needed.
13. What is the difference between bug severity and bug priority?
Bug severity refers to the level of impact that the bug has on the application or system while bug priority refers to the level of urgency in the need for a fix.
14. What is the difference between system testing and integration testing?
For system testing, the entire system as a whole is checked, whereas, for integration testing, the interaction between the individual modules is tested.
15. Explain the term bug.
A bug is an error found while running a program. Bug fall into two categories: logical and syntax.
-: FREE PDF e-Book Download :-
51 JSOM Examples in SharePoint Online
You May Also like the Following SharePoint Online Tutorials: