Fundamentals Of Test Execution and Closure

1. The process of running a test by the component or system under test, producing actual result(s)

Test Execution

Test Closure

Test Design

Test Data Modeling

2. When should you stop testing?

When time for testing has run out.

When all planned tests have been run

When the test completion criteria have been met

When no faults have been found by the tests run

3. The later in the development life cycle a fault is discovered, the more expensive it is to fix. why?

The documentation is poor, so it takes longer to find out what the software is doing.

Wages are rising

The fault has been built into more documentation,code,tests, etc

None of the above

4. The cost of fixing a fault during closure is important ?

Is not important

Increases the later a fault is found

Decreases the later a fault is found

Can never be determined

5. In which order should tests be run?

The most important tests first

The most difficult tests first(to allow maximum time for fixing)

The easiest tests first(to give initial confidence)

The order they are thought of

6. Faults found by users are due to:

Poor quality software

Poor testing

Bad luck

Insufficient time for testing

7. Output for test execution are

Test Log

Defect report

Test cases

None

8. Which of the following is a static test?

Code inspection

Coverage analysis

Installation test

Usability assessment

9. A set of several test cases for a component or system under test, where the post condition of one test is often used as the precondition for the next one

Test suite

Test case

Test log

Defect report

10. In which document where the Test Results are recorded?

Test case

Test log

Test report

Test suite

11. What is the management tool:

QTP

Load Runner

QC

Win runner

12. A document identifying test items, their configuration, and other delivery information delivered by development to testing, at the start of a test execution phase

Release notes

Release content specification

Release summary report

13. Incidents would not be raised against

Requirements

Documentation

Test cases

Improvements suggested by users

14. Which of the following statements is true?

Faults in program specifications are the most expensive to fix.

Faults in code are the most expensive to fix.

Faults in requirements are the most expensive to fix

Faults in designs are the most expensive to fix.

15. A program with high cyclometic complexity is almost likely to be:

Large

Small

Difficult to write

Difficult to test

16. A typical commercial test execution tool would be able to perform all of the following, EXCEPT:

Calculating expected outputs

Comparison of expected outcomes with actual outcomes

Recording test inputs

Reading test values from a data file

17. Which of the following is NOT included in the Test Plan document of the Test Documentation Standard?

What is not to be tested

Test environment properties

Quality plans

Schedules and deadlines

18. What is the purpose of qtp?

Just to run applications

Just to find results fast

Just to complete work fast

Just to find exact solution

19. What is the main reason for testing software before releasing it?

To show that system will work after release

To decide when the software is of sufficient quality to release

To find as many bugs as possible before release

To give information for a risk based decision about release

20. What type of review requires formal entry and exit criteria, including metrics:

Walkthrough

Inspection

Management review

Post project review