General Software testing interview questions.

1. Have you used automatic testing tools. Which ones?...
Project sizes are becoming big and as continuous enhancements are happening Automation scripts are playing major role in the Testing.
Apart form the Functionality testing tools are used in Performance testing to a great extent. Coming to your question we are using.Mercury tools to test the functionality and performance of windows client(Messenger) and dashboards apart form this we are using telecom stress tools to test the telecom server functionality these tools are developed internally depends as per the requirement. We are using Mercury’s Test directory for test management.

2. How would you build a test with WinRunner? Rational Visual Test?
In WinRunner we have to use checkpoint for building a testcase.

3. What is considered a good test?
1.A good test must ensure error-free and reliable functioning of the software.
2. A good test must be completed in optimum time and cost.
3. Not redundant.
4. The probablity of finding an error is minimised to a great extent.

4. How would you conduct a test: top-down or down-top? What is it? Which one is better?
This concept comes in the integration testing the perpouse of integration testing is combing deffirant modules in our project and cheek the funcationality
In top - down approach testing is conducted from main moduel to sub moduel
In bottom - up appoch testing is conducted from submoduel to main moduel
assume that your project has three modules
example for top - down
m1 -> m2 -> m3 etc
bottom - up
m3 -> m2 -> m1

5. How to develop a test plan ? How to develop a test case?
Test plant is prepared by test lead after completion of test initiation.
in that test plan test lead follows some factors. they are:
1. team formation,
2. analyse tactical risks
3. prepare test plan and
4. review test plan.

6. How do you see a QA role in the product development life cycle?
The role of QA :
Preparing Test Strategy
Preparing Test Methodology
Preparing Test Plan

7. What is the size of your executable?
Size of release or size of executabe referes to the Kilo line of the code (number of line written for the application )is mentioned in the kilo line , we can eloborate this as
Eg for a module A Total line =(coded line+ commented line +blank line )
in which the No. of blank lines can be ignored

8. What version of Oracle database did you use?
SQL> select banner from V$version;This is the command to know "what Version we are working"

9. How would you execute a SQL query in Oracle 8?
We can execute any SQL queries using the SQL editor or TOAD or SQL*Plus....

10. What version of OS were you using?
Windows XP.

11. Have you tested front-end of back-end?
Both.Generally we check Front end, but functionality is always work in combination with back end.

12. What was the most difficult problem you ever found while testing?
Sometimes some bugs are not reproducible, this is the worst case i feel when that bug not get fixed.

13. What were you responsible to test in your previous company?
Involved in Manual Testing part :
The following are my responsibilities:
1. Understanding the Functional, Specification and Design documents
2. Preparing the Requirement Traceability matrix and Test Plan
3. Test Case Preparation: Main goal is to cover each and every requirement, test cases are prepared according to the Test case standards (means Font size- Arial10, the name of the test case should be short and descriptive, without spelling and grammar mistakes etc), every requirement should have at least one test case, test cases must be prepared for all valid, invalid, expected and unexpected scenario’s, should be prepared based on the Test case template (Test case Id, Test case name, precondition, description, steps, input, Expected result, actual output, status(pass/fail), designer, date and time, application name, module name, version, Remarks)
4. Test Case Execution: Executing the Test case for particular scenario to decide the variation between the Expected Result and actual output. And to decide whether the given input is producing the expected output. And to analyze the application as per the requirement
5. Analyzing the Test Results: Analyze the results to find out is there any difference between actual and expected result. To find out the bugs. To check whether all the customer requirements are satisfied
6. Report the bugs and Log the bugs in the Defect Tracker: Usually Test Director,Sanity Testing: Test the application to decide whether it is ready for testing, whether the major functionalities are working or not, it is the initial testing
7. Retesting: Testing the application or module to check whether the reported bug is solved/ rectified or not
8. Regression Testing: Testing the application whether the major bug is solved and to check whether any new bugs are introduced
9. Functional Testing: Testing the application to check whether all the functional requirements are satisfied or testing the application according to the functionality
10. Bug report generation: Analyze the test results, findout the bugs, log them in the Defect Tracker, generate the report
11. Issue raising and resolving: while understanding the application, is at all any doubts, raise them and conduct discussions with the higher authority or team members and get them resolved


14. Why do you like to test?
Testing is my pleasure.I think here i have to phase new challenges daily and i really like it.

15. How would you conduct your test?
To conduct a test; first and most importing thing is test bed.

16. What is the difference between testing and debugging?
Testing: It is done by Tester to evaluating the efficiency,accuracy , performance of the developed project/soetware and genrating a report for that softawre. whatever errors arrises during the testing ll be send to developer. Developer have to solve that problems and send back to tester...this process goes continious until tester generate an error free report.

Debugging: It is done by the Developer. Here developer fixing the bugs, which arrives through tester/user/programmer during debugging time