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 the Touchstone application with all major web browsers

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

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

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

Excessive defect rate or defectcorrection defect correction time

Extend testing windowif window if possible.   If not possible then execute test cases inunrelatedin unrelated/unblocked functional areas of the application based on designatedprioritydesignated priority.   Identify problem areas and ensure that additional attention isfocused is focused on these areas for regression testing.

Type of Testing

Included
Y/N

Comments

Team Responsible

Automation

N

MIT personnel will utilize jMeter to automate portions of the backend testing; no test automation tools will be used for the UI testing (use of Flash prevents this).

N/A

Conversion

N

There is no pre-existing system, ; therefore no data conversion is necessary.

N/A

Exploratory

Y

Some level of exploratory testing will be conducted based on heuristics related to typical rich-content internet applications.

Questcon

Functional

Y

Functional testing will be performed based on test cases derived on the documented use cases and front-end functional design.

Questcon

Installation / Upgrade

N

Because this is a web application no installation testing is necessary.

N/A

Integration

Y

Some integration testing will naturally occur as the front-end of the Touchstone application interfaces with and utilizes the back-end APIs.

Questcon

Parallel

N

There is no existing system that Touchstone is replacing.

N/A

Performance

N

Performance testing is coved by a separate Test Plan.

N/A

Regression

Y

Questcon expects to run at least a minimum regression test set prior to release to production.

Questcon

Security

Y

Backend security testing will be done by MIT.   Questcon will execute basic security/login testing on the front-end

MIT - Tester (backend)
Questcon (front-end)

UAT

Y

The user community will be tasked with performing ad-hoc user acceptance testing, domain specific metadata testing (metadata titles, tag lists, etc.),   as well as previously designated documented functional test cases for multiple browser/OS configurations (primarily Safari or Firefox/Mac configurations).

MIT - User Community

Unit

Y

Questcon expects the MIT developers to perform unit testing prior to releasing code to the test environment.

MIT - Developers

Hardware

O/S

Other

PC

Windows XP Professional SP 2

• Mozilla Firefox v2+
• Microsoft IE v6+
• Adobe Flash v9+1

Macintosh PowerPC

Mac OS X

• Firefox v2+
• IE v6+
• Flash v9+ 
• Safari v2+

Key Deliverables

 Description Description

Expected Delivery Date

Resource

Test Plan

This document.

TBD

TBD

Test Case Designs

List of objectives and priorities of the tests.

TBD

TBD

Test Cases

Steps and expected results.

TBD

TBD

Status Reports

Accomplishments, issues and plans.

Weekly

TBD

Test Logs

Run logs.

Ongoing during test execution

TBD

Defect Reports

Entered in Jira as they are discovered.

Ongoing during test execution

TBD

Test Summary Report

Details the results of the testing effort.

TBD

TBD