Software Testing Interview Answers
- What is the MAIN benefit of designing tests early in the life cycle?
Designing tests early in the life cycle can prevent defects from being introduced into the code.
- What is risk-based testing?
Risk-based testing is the term used for an approach to creating a test strategy that is based on prioritizing tests by risk. The basis of the approach is a detailed risk analysis and prioritizing of risks by risk level. Tests to address each risk are then specified, starting with the highest risk first.
- What is the KEY difference between preventative and reactive approaches to testing?
Preventative tests are designed early whereas reactive tests are designed after the software has been produced
- What is the purpose of exit criteria?
An exit criterion defines when a test level is complete.
- What determines the level of risk?
The likelihood of an adverse event and the impact of the event determine the level of risk.
- When is used Decision table testing?
Decision table testing is used for testing systems for which the specification takes the form of rules or cause-effect combinations. In a decision table the inputs are listed in a column, with the outputs in the same column but below the inputs. The remainder of the table explores combinations of inputs to define the outputs produced.
- What is beta testing?
Beta testing is testing that is performed by potential customers at their own locations.
- Which is a benefit of test independence?
It avoids author bias in defining effective tests.
- What is component testing?
Component testing, also known as unit, module and program testing, searches for defects in, and verifies the functioning of software (e.g. modules, programs, objects, classes, etc.) that are able to be tested separately. Component testing may be done in isolation from the rest of the system depending on the context of the development life cycle and the system.
- What is functional system testing?
Testing the end to end functionality of the system as a whole.
- What are the benefits of Independent Testing
Independent testers are unbiased.
- In a reactive approach to testing when would you expect the bulk of the test design work to be implemented?
After the software or system has been produced.
- When should configuration management procedures be implemented?
During test planning.
- What are the white-box testing techniques?
White-box testing techniques use the internal structure of the software to derive test cases. They are commonly called 'glass-box' techniques (implying you can see into the system) since they require knowledge of how the software works.
- How much testing is enough?
It depends on the risks, contract and special requirements.
- What is exploratory testing?
Exploratory testing is a hands-on approach in which testers are involved in minimum planning and maximum test execution. The planning involves the creation of a test charter, a short declaration of the scope of a short (1 to 2 hour) time-boxed test effort, the objectives and possible approaches to be used. The test design and test execution activities are performed in parallel typically without formally documenting the test conditions, test cases or test scripts. This does not mean that other, more formal testing techniques will not be used. Some notes will be written during the exploratory-testing session, so that a report can be produced afterwards.
- What is failure?
Failure is the deviation from expected result to actual result
