Interview questions on Software Testing - VOL-I

Q.1  Explain test comparators.

Ans:  The essence of testing is to check whether the 

software gives the correct result or not, and to do that, we should compare what the software outputs to what it should produce. A test comparator is helpful in automating aspects of that
comparison.

Q.2  Explain risk-based testing.

Ans:    It is a term used for an approach for creating a test strategy which is based on prioritizing tests by risk.The basis of the approach is a detailed risk analysis and prioritizing of possible risks by risk level.

Q.3  Give some MOST important advantage of independence in testing?

Ans:  An independent tester can be more effective in finding defects missed by the person who has written the software. 

Q.4  In which sequence should tests be run?

Ans:  Most important tests should be first 

Q.5  Explain Boundary value testing.

Ans:  Testing all boundary conditions on, above and below the edges of output and input equivalence classes.

Q.6  Explain Alpha testing.

Ans:  It is performed at developer’s site. It is a per-release testing by end user representatives.

Q.7  Explain test coverage.

Ans:  Test coverage measures in some specific way the amount of testing performed by a set of tests (derived in some other way, e.g. using specification-based techniques). Wherever we
can count things and can tell whether or not each of those things has been tested by some test, then we can measure coverage. 

Q.8  What is maintenance testing?

Ans:  Triggered by modifications, migration or retirement of existing software.

Q.9  What is the difference between re-testing and regression testing?

Ans:  Re-testing ensures the original fault has been removed; regression testing looks for unexpected side-effects. 

Q.10  What is the difference between use case, test case, test plan?

Ans:  Use Case: It is prepared by Business analyst in the Functional Requirement Specification(FRS), which are nothing but a steps which are given by the customer.
Test cases: It is prepared by test engineer based on the use cases from FRS to check the functionality of an application thoroughly
Test Plan: Team lead prepares test plan, in it he represents the scope of the test, what to test and what not to test, scheduling, what to test using automation etc.

Q.11  What is the purpose of test design technique?

Ans:  Identifying test conditions and Identifying test cases

Q.12  Why can be tester dependent on configuration management?

Ans:  Because configuration management assures that we know the exact version of the testware and the test object.

Q.13  What do you mean by reproducing the bug? If the bug was not reproducible, what is the next step?

Ans:  If you find a defect, for example click the button and the corresponding action didn’t happen, it is a bug. If the developer is unable to find this behaviour he will ask us to reproduce the bug. In another scenario, if the client complaints a defect in the production we will have to reproduce it in test environment.
If the bug was not reproducible by developer, then bug is assigned back to reporter or goto meeting or informal meeting (like walkthrough) is arranged in order to reproduce the bug. Sometimes the bugs are inconsistent, so that that case we can mark the bugs as inconsistent and temporarily close the bug with status working fine now.

Q.14  What are the Experience-based testing techniques ?

Ans:  In experience-based techniques, people's knowledge, skills and background are a prime contributor to the test conditions and test cases. The experience of both technical and business people is important, as they bring different perspectives to the test analysis and design process. Due to previous experience with similar systems, they may have insights into what could go wrong, which is very useful for testing.

Q.15  . How to launch the test cases in Quality Centre (Test Director) and where it is saved?

Ans:  You create the test cases in the test plan tab and link them to the requirements in the requirement tab. Once the test cases are ready we change the status to ready and go to the “Test Lab” Tab and create a test set and add the test cases to the test set and you can run from there.For automation, in test plan, create a new automated test and launch the tool and create the script and save it and you can run from the test lab the same way as you did for the manual test cases.The test cases are sorted in test plan tab or more precisely in the test director, lets say quality centers database. test director is now referred to as quality center.

 
Design by Free WordPress Themes | Bloggerized by Lasantha - Premium Blogger Themes | Best Hostgator Coupon Code