Page History

Risk

Contingency

QA environment not available

Utilize development or production environment

Insufficient time to fully test the Touchstone application with all major web browsers

Execute ~80% of application functionality with MIT's standard browser (Mozilla Firefox 2.0) and ~20% of the functionality with other browsers.

Test time increases due to changes in scope requiring additional test analysis and/or test case creation

If test time cannot be increased, reduce/cut overlap in multi-browser testing and execute highest priority test cases initially followed by lower priority tests until test time runs out

Excessive defect rate or defect correction time

Execute test cases in unrelated/unblocked functional areas of the application based on designated priority

Insufficient time to fully test theTouchstone application with all major web browsers

Prioritize the risk ofthe functionality to be tested.  Identify high risk functionality and ensurethat high risk items are tested thoroughly.  All high priority items willbe tested in both browsers.  As time permits additional functionality willbe tested based priority and risk with the most attention focused on theMozilla browser.

Test time increases due to changesin scope requiring additional test analysis and/or test case creation

If test time cannot beincreased, reevaluate priorities and risk and test according to new priorities.

Excessive defect rate or defectcorrection time

Extend testing windowif possible.  If not possible then execute test cases inunrelated/unblocked functional areas of the application based on designatedpriority.  Identify problem areas and ensure that additional attention isfocused on these areas for regression testing.

Key Deliverables

Expected Delivery Date

Resource

Functional Test Tree (FTT)

TBD

TBD

Test Plan

TBD

TBD

Test Case Designs

TBD

TBD

Test Cases

TBD

TBD

Status Reports

Weekly

TBD

Test Logs

Ongoing during test execution

TBD

Defect Reports

Ongoing during test execution

TBD

Test Summary Report

TBD

TBD

Milestone

Target Timeframe

Summation of Activities

Develop test strategy / plan

//2008 - //2008

• Analyze existing design documents, notes, and other available materials
• Develop test plan document
  

Review test plan

//2008 - //2008

• Review, clarify, correct, and update the test plan
• Client approval of test plan

Perform test analysis

//2008 - //2008

• Develop FTT
• Develop test case design document

Review FTT & test case design

//2008 - //2008

•  ReviewReview, clarify, correct, and update the test case design

Build functional test cases / scenarios

//2008 - //2008

• Combine test objectives into test cases
• Document data, procedures, and results
• Prioritize test cases
• Determine which test cases will be executed in different browser/OS configurations

Setup test environment

//2008 - //2008

• Setup web server and database server
• Load application under test
• Setup logins and authorizations

Setup test data

//2008 - //2008

• Review & analyze test cases to target data to load in test environment
• Load initial test data set

Execute functional & exploratory tests

//2008 - //2008

• Execute documented test cases, as well as exploratory tests
• Communicate with the development team when issues are found
• Maintain a test run log
• Track test metrics

Investigate / correct defects

//2008 - //2008

• Investigate and validate that a defect has been found
• Log defects in Jira
• Work with the development team, as necessary, to identify the cause of the defect
• Accept and retest defect corrections from the development team

Execute regression tests

//2008 - //2008

• Execute a prioritized subset of test cases as regression of the system once all functional and exploratory testing is complete
• Validate that no new errors have been introduced as a result of correcting known defects or configuration management / version control issues
• Investigate and validate that a defect has been found
• Log defects in Jira
• Work with the development team, as necessary, to identify the cause of the defect
• Accept and retest defect corrections from the development team

Execute UAT

//2008 - //2008

• Work with the user community to identify and manage the execution of user acceptance tests
• Communicate with the development team when issues are found
• Investigate and validate that a defect has been found
• Log defects in Jira
• Work with the development team, as necessary, to identify the cause of the defect
• Accept and retest defect corrections from the development team

Create test summary

//2008 - //2008

• Create and deliver a test summary report to include:
  • Summation of planned/actual test activities
  • Deviation from planned activities
  • Summary of defects (open defects)
  • Summary of test metrics