Test Plans

1
Test Plans

• Jackson T, Terry G, Jelana P

2
Contents

• Principles involved
• Types of test plans
• Sample test plan

3
Principles Involved

• A software project test plan is a document that
  describes the objectives, scope, approach and
  focus of a software testing effort.
• The process of preparing a test plan is a useful
  way to think through the efforts needed to
  validate the acceptability of a software product.
  
• The completed document will help people outside
  the test group understand the why and how of
  product validation.
• It should be thorough enough to be useful, but
  not so thorough that none outside the test group
  will be able to read it.

4
Types of Test Plans

• Unit Tests
• Integration Tests
• System Tests
• Acceptance Tests

5
Sample Test Plan

• BACKGROUND Online of the month club
• INTRODUCTION test plan for website
• ASSUMPTIONS user can subscribe to a monthly
  service
• TEST ITEMS
• Registration process
• Check out procedure
• Payment options
• FEATURES TO BE TESTED
• First Name, last name, address, city, country,
  etc.
• Service
• Coffee
• Membership
• Subscriptions
• Username, password
• FEATURES NOT TO BE TESTED
• Web site functionality should be working
• Images and links assumed working
• APPROACH
• User can subscribe to 3, 6, or 12month membership

6
Sample (contd)

• ITEM PASS/FAIL CRITERIA
• Valid member information must be provided
• Payment information must be validated
• At least one subscription must be selected
• TEST DELIVERABLES
• Products Incl. games, wine, coffee.
• Receipts.
• Test report
• Test software
• ENVIRONMENTAL NEEDS
• Computer all peripherals.
• ASP.Net, Server, Internet connection.

7
Sample (contd)

• RESPONSIBILITIES
• Programmers will make the code
• Administration will run the site
• Users will test.
• Programmers will debug.
• STAFFING TRAINING
• Admin will maintain site and train all staff
• SCHEDULE
• Testing will be implemented after design phase
  has been completed.
• Mid testing on coding and methods
• Final test run to ensure completion
• RISKS CONTINGENCIES
• System/server crashes
• System must be up 24/7
• APPROVALS
• Done by management - Jackson

8
Conclusion

• All programs must be throughly tested before they
  are sold or submitted for a grade. Do not rush
  the development of a program and hand it in
  before it has been tested. You still have a
  chance to debug your program if you learn that
  you have an error from administering the test
  plan.
• Thank you for your time.
• Q/A?
• Applause