1. What are the components of an SRS?

An SRS contains the following basic components:

Introduction

Overall Description

External Interface Requirements

System Requirements

System Features

2. What is the difference between a test plan and a QA plan?

A test plan lays out what is to be done to test the product and includes how quality control will work to identify errors and defects.  A QA plan on the other hand is more concerned with prevention of errors and defects rather than testing and fixing them.

3. How do you 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 that work on 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. How can you tell when enough test cases have been created to adequately test a system or module?

You can tell that enough test cases have been created when there is at least one test case to cover every requirement.  This ensures that all designed features of the application are being tested.

6. Who approves test cases?

The approver of test cases varies from one organization to the next. In some organizations, the QA lead may approve the test cases while another approves them as part of peer reviews.

7. 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.

8. Who writes test plans and test cases?

Test plans are typically written by the quality assurance lead while testers usually write test cases.

9. Is quality assurance and testing the same?

Quality assurance and testing is 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.

 

<h2><em><span style=”text-decoration: underline;”>Typical Manual Testing Interview Questions:</span></em></h2>

&nbsp;

10. 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.

11. If an application is in production, and one module of code is modified, is it necessary to retest just that module or should all of the other modules be tested as well?

It is a good idea to perform regression testing and to check all of the other modules as well.  At the least, system testing should be performed.

12. What should be included in a test strategy?

The test strategy includes a plan for how to test the application and exactly what will be tested (user interface, modules, processes, etc.).  It establishes limits for testing and indicates whether manual or automated testing will be used.

13. What can be done to develop a test for a system if there are no functional specifications or any system and development documents?

When there are no functional specifications or system development documents, the tester should familiarize themselves with the product and the code.  It may also be helpful to perform research to find similar products on the market.

14. What are the functional testing types?

The following are the types of functional testing:

Compatibility

Configuration

Error handling

Functionality

Input domain

Installation

Inter-systems

Recovery

15. What is the difference between sanity testing and smoke testing?

When sanity testing is conducted, the product is sent through a preliminary round of testing with the test group in order to check the basic functionality such as button functionality.  Smoke testing, on the other hand is conducted by developers based on the requirements of the client.

16. Explain 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.

17. Define smoke testing.

Smoke testing is a form of software testing that is not exhaustive and checks only the most crucial components of the software but does not check in more detail.

&nbsp;

<h3><span style=”text-decoration: underline;”>Adva<em>nced Manual Testing Interview Questions</em></span></h3>

&nbsp;

18. What steps are involved in sanity testing?

Sanity testing is very similar to smoke testing. It is the initial testing of a component or application that is done to make sure that it is functioning at the most basic level and it is stable enough to continue more detailed testing.

19. What is the difference between WinRunner and Rational Robot?

WinRunner is a functional test tool but Rational Robot is capable of both functional and performance testing. Also, WinRunner has 4 verification points and Rational Robot has 13 verification points.

20. What is the purpose of the testing process?

The purpose of the testing process is to verifying that input data produces the anticipated output.