Assignment on-

Project Test Plan

Submitted toMohammad Ashik Elahi Course Coordinator SE 605

Submitted byGroup 01
Group Members: BIT 0201, BIT 0207, BIT 0210, BIT 0213 BIT 0216, BIT 0219, BIT 0222, BIT 0225, BIT 0228, BIT 0231, BIT 0234

[Date: 05-11-2012]

Institute of Information Technology University of Dhaka

Introduction:
The test plans are like other software documentation. They are dynamic in nature and must be kept up to date. Therefore, the will have revision number. Here the test plan of the project under taken named Student Information System (SIS) for Institute of Information Technology has been developed. Though there are several standard formats to develop any test plan, we the group members of testing plans have decided to use our own way to develop the test plan. With a lot of lack in testing we will try to make the test plan as good as possible for the testers. The test plan will be documented in a structural way using step by step technique. Having limited experience we have tried our best to make the test plan as useful as possible. The test plan described below in an informal way using sequential structure.

Gathering available resources

The first task for developing the test plan is to gather the available resources that should have. The resources should be the product itself, its requirement specification, all the documents to know about the product from which we can extract the features for testing and other different works.

Feature Extraction from those resources

When all the resources of the product are available then the main task is to extract the features of the product. The requirement specification can help here a lot. Specification based testing can be performed using the software requirement specification (SRS). The feature extraction helps the development team to understand the product correctly in a section by section manner which is very much helpful for developing the test cases.

Risk analysis process overview

After extracting the features of the product risk analysis is important. The extracted featured can be analyzed for analyzing where the risk is available. The main task of risk analysis is to guess where the different types of errors are available, differentiate what kinds of errors may have on

those sections. To develop the risk analysis process different mind mapper is used to give the possible error list in a pictured view. To perform this task, a strong team should be build who will follow the 9 steps of risk analysis process overview. The most important steps of this is form a strong brainstorming team, then make them free to give their opinion, take their opinion for consideration, identify the risk items, give them numerical value using likelihood and using other criteria, then making the risk analysis metrics. The risk analysis metrics help to identify which item is the most important to test. In this way we can find out which extracted item should test first, which is not so much important to test, which should be tested or which should not be tested. After completing the above process we can tell that we have now the targeted elements to start the test.

Creating the schedule and the test cases

When the risk metrics is available to the test team they need to create a schedule for performing the test. After then the most important work is to create test plan. To create the test plan we have several tools to make the process very easy. Testlink is a test management system which is helpful for this kind of work. Many other tools are useful to perform this kind of work. Creating and managing the test cases in a scheduled manner is very important task in this section. Who will be responsible, who will execute the test plan, these issues is important here.

Execute the test cases

After having the test cases ready the main task is to execute those test cased in the main product. This can be done manually as well as some automation technique is available for this. Different type of test management system, issue tracking system is useful for this kind of work. Testlink, mantis, bugzilla, readmine etc. are some important tools to perform this kind of work. The test cases can be tested group wise using the session tester which will be more item focus based testing technique. This will help to be focused with the test cases or test items. In this way the different test cases for the different test items are tested and make their report for the future use.

More other testing criteria can be performed using some other tools such as performance, load or stress testing etc. are important aspect of testing a product. Here badboy, which is a testing tools. This is important in this case.

Generate the report and test log

After all these test technique performed, the main task is to generate or log the report. Which test case has been failed or which is passed this will be documented for the developers. Moreover a fully functional test report is generated using this.

Developers work now

Now the final test report is submitted to the developers for fixing the errors the product still have. The developers take the report, review it and fix the errors. Finally, a well-tested product is delivered to the customer.