Versions Compared

Old Version 20

changes.mady.by.user Will Smithee

Saved on

compared with

New Version 21

changes.mady.by.user Will Smithee

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Each of the following UI components and front end functionality developed as part of the Touchstone project will be tested:

  • CAMS Use Cases (IdPe)
    • Self-initiated account creation
    • Users that specify an MIT email address will have their MIT ID number automatically associated with the CAMS account
    • Self service password reset
    • User may register an OpenID account
    • User may set or modify full name information
    • User may associate MIT ID number with account
    • Accounts manager password reset
    • Accounts manager may associate MIT ID number with account
    • User may associate alternate security IDs with the account
    • User may associate other email addresses with their account
    • Administrators may set the status of alt_security_id types
    • OverView of Account Admin
    • Account Deactivation
  • IdPi Use Cases
    • TBD

...

Questcon anticipates the following server and client configurations for the QA environment:

All To Be Determined (TBD) values will be updated once MIT provides the necessary information.

3.3.1 IdPe Server Configuration

...

Key Deliverables

Description

Expected Delivery Date

Resource

Test Plan

This document.

TBD

After all needed data is delivered

Questcon TBD

Test Case Designs

List of objectives and priorities of the tests. TBD .

4 business days after test plan is approved and necessary information and environmental needs met.
This is based off an estimated 250 test cases.

TBD

Test Cases

Steps and expected results. TBD

6 business days after test case design completeion.
This is based off an estimated 250 test cases.

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

2 business days after test execution is completed.

TBD

4.2 Test Schedule

The planned test schedule of the Touchstone project has an anticipated start date of //2008 and completion date of //2008. The estimated completion date is based on several assumptions, some of which have been identified in 2.3 Risks & Contingencies.

Milestone

Target Timeframe

Summation of Activities

Develop test strategy / plan

01/15/2008 - 02/05/2008

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

Review test plan

02/05/2008 - 02/11/2008

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

Perform test analysis

//2008 - //2008
~ 4 business days

  • Develop test case design document

Review test case design

//2008 - //2008

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

Build functional test cases / scenarios

//2008 - //2008
 ~ 6 business days

  • 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
~6 business days 

  • 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
~1 business day

  • 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
2 business days

  • 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