1)Test Documentation: It is a complete suite of documents that allows you to describe and document test planning, test design, test execution, test results that are drawn from the testing activity.

2)Types of Test Documentation:

a) Test Policy: It is a high-level document which describes principles, methods and all the important testing goals of the organization.

b) Test strategy: A high-level document which identifies the Test Levels (types) to be executed for the project.

c) Test plan: A test plan is a complete planning document which contains the scope, approach, resources, schedule, etc. of testing activities.

d) Requirements Traceability Matrix: This is a document which connects the requirements to the test cases.

e) Test Scenario: A Test Scenario is defined as any functionality that can be tested one or more test cases.

f) Test Case: It is a group of input values, execution preconditions, expected execution postconditions and results. It is developed for a Test Scenario.

g) Test Data: Test Data is a data which exists before a test is executed. It used to execute the test case.

h) Defect Report: Defect report is a documented report of any flaw in a Software System which fails to perform its expected function.

i) Test summary report: Test summary report is a high-level document which summarizes testing activities conducted as well as the test result.

3) Boundary Value Analysis: Boundary value analysis is based on testing at the boundaries between partitions. It includes maximum, minimum, inside or outside boundaries, typical values and error values.

Example: Input condition is valid between 1 to 100

                Boundary values 0,1,2 and 99,100,101

4) Equivalence Class Partitioning: Equivalent Class Partitioning allows you to divide set of test condition into a partition which should be considered the same.

Example: Input conditions are valid between: 1 to 10 and 20 to 30

Hence there are five equivalence classes:

Less than 0 to 0 (invalid)

1 to 10 (valid)

11 to 19 (invalid)

20 to 30 (valid)

31 to greater than 31 (invalid)

You select values from each class, i.e.:

-2, 3, 15, 25, 45

5) Decision Table Based Testing: A decision table is also known as to Cause-Effect table. This software testing technique is used for functions which respond to a combination of inputs or events.

Example: How to make Decision Base Table for Login Screen

Let’s create a decision table for a login screen.

Decision Base Table for Login Screen:

The condition is simple if the user provides the correct username and password the user will be redirected to the homepage. If any of the input is wrong, an error message will be displayed.

Conditions              Rule 1 Rule 2 Rule 3  Rule 4

Username (T/F)          F         T         F         T

Password (T/F)          F         F         T         T

Output (E/H)              E       E         E        H

Legend:

T – Correct username/password

F – Wrong username/password

E – Error message is displayed

H – Home screen is displayed

Interpretation:

Case 1 – Username and password both were wrong. The user is shown an error message.

Case 2 – Username was correct, but the password was wrong. The user is shown an error message.

Case 3 – Username was wrong, but the password was correct. The user is shown an error message.

Case 4 – Username and password both were correct, and the user navigated to the homepage.