Test plan
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Test plan

  • 647 views
Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
647
On Slideshare
647
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
7
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Assignment on- Project Test Plan Submitted to- Mohammad Ashik Elahi Course Coordinator SE 605 Submitted by- Group 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
  • 2. Introduction:The test plans are like other software documentation. They are dynamic in nature and must bekept up to date. Therefore, the will have revision number. Here the test plan of the project undertaken named Student Information System (SIS) for Institute of Information Technology hasbeen developed. Though there are several standard formats to develop any test plan, we thegroup members of testing plans have decided to use our own way to develop the test plan. With alot 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. Havinglimited experience we have tried our best to make the test plan as useful as possible. The testplan described below in an informal way using sequential structure.Gathering available resourcesThe 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 toknow about the product from which we can extract the features for testing and other differentworks.Feature Extraction from those resourcesWhen all the resources of the product are available then the main task is to extract the features ofthe product. The requirement specification can help here a lot. Specification based testing can beperformed using the software requirement specification (SRS). The feature extraction helps thedevelopment team to understand the product correctly in a section by section manner which isvery much helpful for developing the test cases.Risk analysis process overviewAfter extracting the features of the product risk analysis is important. The extracted featured canbe analyzed for analyzing where the risk is available. The main task of risk analysis is to guesswhere the different types of errors are available, differentiate what kinds of errors may have on
  • 3. those sections. To develop the risk analysis process different mind mapper is used to give thepossible error list in a pictured view.To perform this task, a strong team should be build who will follow the 9 steps of risk analysisprocess overview. The most important steps of this is form a strong brainstorming team, thenmake 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 riskanalysis metrics. The risk analysis metrics help to identify which item is the most important totest.In this way we can find out which extracted item should test first, which is not so muchimportant to test, which should be tested or which should not be tested. After completing theabove process we can tell that we have now the targeted elements to start the test.Creating the schedule and the test casesWhen the risk metrics is available to the test team they need to create a schedule for performingthe test. After then the most important work is to create test plan. To create the test plan we haveseveral tools to make the process very easy. Testlink is a test management system which ishelpful for this kind of work. Many other tools are useful to perform this kind of work. Creatingand managing the test cases in a scheduled manner is very important task in this section. Whowill be responsible, who will execute the test plan, these issues is important here.Execute the test casesAfter 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. Differenttype 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 testcases can be tested group wise using the session tester which will be more item focus basedtesting technique. This will help to be focused with the test cases or test items. In this way thedifferent test cases for the different test items are tested and make their report for the future use.
  • 4. More other testing criteria can be performed using some other tools such as performance, load orstress 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 logAfter all these test technique performed, the main task is to generate or log the report. Which testcase has been failed or which is passed this will be documented for the developers. Moreover afully functional test report is generated using this.Developers work nowNow 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 isdelivered to the customer.