1. Test case is a group of input values, execution preconditions, expected execution postconditions and results. It is developed for a Test Scenario.

2. Requirement traceability matrix is a document which connects the requirements to the test cases.

3. Defect report is a documented report of any flaw in a Software System which fails to perform its expected function

4. Risk plan is a complete planning document which contains the scope, approach, resources, schedule, etc. of testing activities.

5. Use case is a brief description of a particular use of the software application by an actor or user.

6. Test estimation is a management activity which approximates how long a Task would take to complete.

Pass rate is the ratio between number test cases executed/total test cases of test specification.

8. Equivalent class analysis is a software testing technique that is based on testing at the boundaries between partitions.

9. In state transition testing technique, changes in input conditions change the state of the Application Under Test (AUT).

10. Equivalent class partitioning allows you to divide set of test condition into a partition which should be considered the same.

11. Error guessing is based on guessing the error which can prevail in the code.

Test summary is used for functions which respond to a combination of inputs or events.

13. defect is a variation or deviation of the software application from end user’s requirements or original business requirements.

Run rate is the ratio between numbers test cases passed / test cases executed.

15. Exit criteria specifies the criteria that denote a successful completion of a test phase.

16. Test summary is a high-level document which describes principles, methods and all the important testing goals of the organization.

17. Test data is a data which exists before a test is executed. It used to execute the test case.

Test strategy report is a high-level document which summarizes testing activities conducted as well as the test result.

Test summary is a high-level document which identifies the Test Levels (types) to be executed for the project.

20. Test scenario is an item or event of a software system which could be verified by one or more Test cases.

21. Test documents are also known as

22. Testing is

23. The degree of test formality depends on

25. a test strategy is

24. Testing activities generally consume _______ of software development project effort.

____ divides a complex project into modules.

27. To estimate the ___ of the task, the test manager has to give weightage to each functional point.

_____ is divided into multiple test plans that are taken care further independently.

29. In three-point estimation, ___ is used to know the probability that the estimation is correct.

In ___ , the test manager estimates the size, duration, and cost for the tasks.

_____ helps people outside the test team such as developers, business managers, customers understand the details of testing.

___ is used to compute for the task effort in three point estimation.

33. The degree of test formality depends on maturity of the development process.

34. Risk is future’s uncertain event with a probability of occurrence and a potential for loss.

Test report helps to identify similar bugs in future so it can be avoided

36. use ____ to manage and track your documents

___ helps to better communicate, track and explain defects in detail.

38. Before the start of any test activity, ____ should be known.

___ is a step by step process of fixing the defects.