Manual Testing Material

Plan:

Plan is a strategic document, which describes how to perform a task in an effective, efficient and optimized way.

Optimization:

Optimization is a process of reducing or utilizing the input resources to their maximum and getting the maximum possible output.

Test Plan:

It is a strategic document, which describe how to perform testing on an application in an effective, efficient and optimized way. The Test Lead prepares test plan.

CONTANTS OF THE TEST PLAN

INTERDUCTION.
1.1 Objective.
The main purpose of the document is clearly described here in this section.

1.2 Reference Document.
The list of all the documents that are referred to prepare the test plan will be listed out here in this section.

2.0 COVERAGE OF TESTING.
2.1 Features To Be Tested
The list of all the features with in the scope are mentioned here in this section

2.2 Features Not To Be Tested
The lists of all the features that are not planed for testing based on the following criteria are mentioned here in this section.

Out of scope features
Low risk areas
Future functionalities.
The features that are skipped based on the time constraints.
3.0 TEST STRATEGY
It is defined as an organization level term, which is used for testing all the projects in the organization.

TEST PLAN
It is defined as a project level term, which is describes how to test a particular project in an organization.
Note:
Test strategy is common for all the projects. But test plan various from project to project.

3.1 Levels of Testing
The list of all the levels of testing that are maintained in that company are listed out here in this section.

3.2 Types of Testing
The list of all the types of testing that are followed by that company are listed out here in this section.

3.3 Test Design Technique
The list of all the techniques that are followed by that company during the test case development are listed out here in this section.
Ex: BVA (Boundary Value Analysis)
ECP (Equable Class Partition)

3.4 Configuration Management

3.5 Test Metrics
The lists of all the tasks that are measured and maintain in terms of metrics are clearly mentioned here in this section.

3.6 Terminologies
The list of all the terms and the corresponding meanings are listed out here in this section

3.7 Automation plan
The list of all the areas that are planed for automation in that company are listed out her in this section.

3.8 List of Automated Tools
The list of all the automated tools that are used in that company are listed out here in this section.



4.0 BASE CRITERIA
4.1 Acceptance Criteria.
When to stop testing in a full pledged manner thinking then enough testing is done on the application is clearly described here in this section.

4.2 Suspension Criteria.
When to stop testing suddenly and suspended the build will be clearly mentioned here in this section.

5.0 TEST DELIVERABLE.
The list of all the documents that are to be prepared and deliver in the testing phase are listed out here in this section.

6.0 TEST ENVIRONMENT.
The customer specified environment that is about to be used for testing is clearly describes here in this section.

7.0 RESOURCE PLANNING.
Who has to do what is clearly described here in this section.

8.0 SCHEDULING.
The starting dates and the ending dates of each and ever task is clearly described here in this section.

9.0 STAFFING AND TRAINING.
How much staff is to be requited what kind of training is to be provided is clearly planned and mentioned here in this section.

10.0 RISK AND CONTINGENCES.
The list of all the potential risks corresponding solution plans are listed out here in this section.
Risks

Unable to deliver the software with in the dead lines.
Employees may leave the organization in the middle of the project development.
Customer may impose the dead lines.
Unable to test all the features with in the time.
Lake of expatriation.
Contingences

Proper plan ensurence.
People need to be maintained on bench.
What not to be tested has to be planed properly.
Severity priority based execution.
Proper training needs to be provided.
11.0 ASSUMPTIONS.
The list of all the assumptions that are to be assumed by a test engineer will be listed out here in this section.

12.0 APPRUVAL INFORMATION.
Who will approve what is clearly mentioned here in this section.