Đề 11

1. Under limited project time and budget, testing effort shall be focused proportionally to the expected and later observed defect density of modules so that project constraints are properly managed. Which testing principle is explained?

• Pesticide paradox
• Absence-of-errors fallacy
• Early testing
• Defect clustering

2. Debugging and testing are different. Dynamic testing can show failures that are caused by defects. Debugging is the development activity that find, analyzes and removes the cause of the failure. Which of the following is an example of debugging?

• A tester retests a fix from the developer and finds a regression
• A developer performs unit testing
• A tester finds a defect and reports it
• A developer finds and fixes a defect

3. The most visible part of testing is test execution. But to be effective and efficient, test plans should also include time to be spent on planning the tests, designing test cases, preparing for execution and evaluating result. Which of the following is a major task of test planning?

• Determining the test approach
• Preparing test specifications
• Evaluating exit criteria and reporting
• Measuring and analyzing results

4. Which of following statement defines the levels of independence from low to high?

i. Tests designed by a person from an independent test team or performance test specialists

ii. Tests designed by a person from an outsourcing or certification by an external body

iii. Tests designed by the person who wrote the software under test with the low level of independence

iv. Tests designed by another person from development team

• i, ii, iii, iv

• iv, ii, i, ii

• iii, iv, i, ii

• iv, iii, ii, i

5. Which describes about the Pesticide Paradox which is one of the Seven Testing Principles?

• Testing is done differently in different contexts. For example, safety-critical software is tested differently from an e-commerce site
• If the same tests are repeated over again, eventually the same set of test cases will no longer find any new defects. To overcome this, test cases need to be regularly reviewed and revised and new and different tests need to be written to exercise different parts of the software or system to find potentially more defects
• Testing everything (all combinations of inputs and preconditions) is not feasible except for trivial cases. Instead of exhaustive testing, risk analysis and priorities should be used to focus testing efforts
• To find defects early, testing activities shall be started as early as possible in the software or system development life cycle and shall be focused on defined objectives.

6. Which is NOT part of the test execution phase?

• Performing the test basis
• Logging test results
• Reviewing the test basis
• Verify test environment

7. Which of following is NOT about functional testing?

• This testing is considers the external behavior of the software (black-box testing)
• Security testing investigates the functions relating to detection of threats.
• This testing describes the test required to measure characteristics of systems and software that can be quantified on a varying scale.
• Interoperability testing evaluates the capability of the sofware product to interact with one or more specified components or systems.

8. Which of the following statement does NOT correctly describe a valid approach to Component Testing?

• Functional testing of the interfaces between modules
• Functional testing of the component in isolation
• Structure-based testing of the code without recording incidents
• Automated tests that are run until the component passes

9. What is important to do when working with software development models?

• To adapt the models to the context of project and product characteristics
• To choose the waterfall model because it is the first and best proven model
• To start with the V-model and then move to either iterative or incremental models
• To only change the organization to fit the model and not vice versa

10. What are good practices for testing within the development life cycle?

• Testers are involved in document reviews
• Different test levels are defined with specific objectives
• Early test analysis and design
• All of above