Software Testing Interview Questions 3

1. What is the testing process?

Verifying that an input data produce the expected output.

2. What is the difference between testing and debugging?

Big difference is that debugging is carry out by a programmer and the programmer fix the errors through debugging phase. Tester in no way fixes the errors, but rather find them and send to programmer.

3. What is the diversity between structural and functional testing?

Structural is a "white box" testing and base on the algorithm or code. Functional testing is a "black box" (behavioral) testing where the tester validate the functional requirements.

4. What is a bug? What types of bugs do you know?

Bug is an error during execution of the program. There are two kinds of bugs: syntax and logical.

5. Difference between testing and quality assurance (QA)?

This question is startlingly well-liked. However, the answer is pretty simple. The goals of both are different: The goal of testing is to discover the errors. The goal of QA is to put off the errors in the program.

6. What kinds of testing do you make out? Is it system testing? What you mean by integration testing? What is a unit testing? What is a regression testing?

System testing is a testing of the complete system as a whole. This is what user see and feels about the product you offer.

Integration testing is the testing of integration of different modules of the system. Usually, the integration process is quite tender and this testing is the gravest one of all. Integration testing comes previous to system testing.

Unit testing is a testing of a single unit/module of within system. It's carried out previous to integration testing.

Regression testing is a "backward check" testing. The idea to make sure that new functionality added to the system did not break old, checked, functionality of the system.

7. What are all the major processes will engage in testing?

1. Planning (test strategy, test objectives, risk management)

2. Design (functions to be tested, test scenario, test cases)

3. Development (test procedures, test scripts, test environment)

4. Execution (execute test)

5. Evaluation (evaluate test results, compare actual results with expected results)

8. Could you test a program 100%? 90% ? If not then Why?

Definitely not! The main trouble with testing that you cannot compute how many error are in the code, functioning etc. There are many issues involved such as experience of programmer, complications of the system etc.

9. How would you test a mug (chair/table/gas station etc.)?

First of all you have to demand requirements and functional requirement and design document of the mug. There will find requirements like ability to hold hot water, waterproof, stability, break ability and so on. Then you should test the mug according to all documents.