test design 3

1.

1 point

This type of scenarios aim to have a higher probability of detecting errors.

Positive

Negative

Both

None

2.

1 point

This is a preparation to support the test conditions and test cases

Test Data

Test coverage

Test Basis

All of the above

3.

1 point

Testable business scenarios are not translated to business development:

True

False

4.

1 point

A scenario can have multiple test conditions

True

False

5.

1 point

Test Coverage is ensured through test scenarios

false

true true

6.

1 point

Boundary value analysis is often called a part of

None of the above

Negative

Stress

Both a and b

7.

1 point

tells the system about the business rules

none

Transitional

Output

Set Up

8.

1 point

A customer withdraws certain amount from ATM machine. Checking this Transaction through net banking comes under

System Testing

Component

System Integration

9.

1 point

is done by translating business scenarios to reusable set of test scenarios, ensuring coverage and traceability

ACE

Both

Use Case

None

10.

1 point

Each level of testing have its own regression suite

True

False

11.

1 point

Equivalence testing divides the input domain into classes of data from whichtest cases can be derived to reduce the total number of test cases that must be developed

True

False

12.

1 point

Entry Criteria to Test Developement Process

Approved Test plan

Approved Scenarios

Test Data Source

None of the above

13.

1 point

Outcome of Test cases

Revised Test Plan

Procedures for test set up, test excution and restoration

Test Closure Report

Updated RTM

14.

1 point

Use cases can be performed to test

Performance testing

Unit testing

Business scenarios

Static testing

15.

1 point

Test Results can be stored in Test Runs

True

False

16.

1 point

Expected results are

Only important in system testing

Only used in component testing

Most useful when specified in advance

Derived from the code

17.

1 point

Test Data is also important to non functional testing

False

True

18.

1 point

Impact analysis is required

Testing after Bug Fixing

Change to the requirements

Introducing a new module or functionality to an existing product under test

None

19.

1 point

One scenario can be mapped to several test cases

True

False

20.

1 point

Impact Analysis helps to decide

How many more test cases need to written.

How much regression testing should be done.

Exit Criteria

Different Tools to perform Regression Testing

21.

1 point

A user uses a list of countries from selected modules. what data is it?

Transactional

Transitional

Master

None

22.

1 point

Test suites are created and prioritized ,based on the impact caused to the system

True

False

23.

1 point

Boundary value analysis covers equivalence partitioning

True

False

24.

1 point

one which lists out the cause and effect matrix

BVA

None

Decision tables

Equivalence Partioning

25.

1 point

Which type of test would you perform to accept a build for testing?

sanity

smoke

system

beta

26.

1 point

These are grouped into manageable (and schedulable) units called .

Test cycles

None

Test Suite

Both

27.

1 point

Testing of a previously verified program or application following program modification for extension or correction to ensure no new defects have been introduced

None

Regression

Retest

System

28.

1 point

One Requirement can have multiple use cases

True

False

29.

1 point

this is a measure but not a method

Condition

Coverage

Scenario

all of the above

30.

1 point

Test data preparation techniques are

both a and b

none of the above

Permutations

Partitions