...
Each of the following UI components and front end functionality developed as part of the Touchstone project will be tested:
- All 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
2.2.2 Items Not To Be Tested
The following modules and types of tests are considered to be outside the scope of this test effort and will not be tested by Questcon. Testing may be performed by internal MIT personnel:
- CAMS Use Cases (IdPe)
- Sponsored account creation
- Sponsor may review a list of accounts that they have sponsored
- IdPi Use Cases
- TBD
2.3 Risks & Contingencies
...
The overall approach to this test effort will be to validate that the Touchstone UI meets the needs of the user community as a tool for managing images and other digital mediaMIT to provide a mechanisim for single sign on using a federated id. Validation will be performed based on test cases derived from the documented use cases, front-end functional designs, as well as exploratory testing heuristics.
MIT has indicated that the user community is largely standardized on Mozilla's Firefox v2.0 web browser in a PC or Mac environment. Rather than re-executing all tests with each browser, Questcon will execute approximately 80% of the test cases using Firefox and approximately 20% of the tests using IE 6 and 7 (both in a PC/Windows architecture). There will be some overlap in testing and touch points, but not enough to significantly impact the schedule.
Questcon will analyze the test cases to identify the best candidates for execution using IE 6 and 7. IE 6 and 7 test cases will be chosen based on the amount of functionality traversed in the application. In other words Questcon will attempt to "touch" as much of the application as possible using IE 6 and 7.
Furthermore, a significant portion of the user community utilizes the Mac OS X operating system with the Safari browser. Some duplicate testing will be performed by Questcon utilizing Safari and Firefox for the Mac (10% or less). MIT should designate a group of users to execute more tests using the Safari/Mac and Firefox/Mac combination of browser and operating system. Questcon will assist the users in identifying the best tests to execute.
The following table outlines the various types of testing considered for this test effort, any additional comments about the testing, and the individual or group responsible for completing the testing.
Type of Testing | Included | Comments | Team Responsible |
Automation | Y 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). MIT - Tester | 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 | Y N | Performance testing will be done on the back-end APIs and servlets. No front-end performance testing will be done. MIT - Tester 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) |
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 |
...
Tool | Purpose | Used By | ||
Atlassian Jira | Web-based defect tracking system accessed by http://mv.ezproxy.com.ezproxy.canberra.edu.au/jira | Touchstone Project Team (MIT & Questcon) Apache JMeter | Backend performance testing | MIT - Tester |
3.3 Environmental Needs
Questcon anticipates the following server and client configurations for the QA environment:
3.3.1
...
IdPe Server Configuration
...
...
Hardware | O/S | Other |
TBD | TBD |
|
3.3.2
...
IdPi Server Configuration
Hardware | O/S | Other |
HP G4 | Red Hat Enterprise Linux AS release 4 |
|
3.3.3 Database Server Configuration
TBD | TBD |
|
Hardware | O/S | Other |
HP G4 | Red Hat Enterprise Linux AS release 4 |
|
3.3.4 Client Configuration
Hardware | O/S | Other |
PC | Windows XP Professional SP 2 |
|
Macintosh PowerPC | Mac OS X |
|
...
This section identifies the deliverables, delivery date and resource responsible for each deliverable.
Key Deliverables | Expected Delivery Date | Resource | |
Functional Test Tree | 05/04/2007 | TBD | TBD Bill Silver |
Test Plan | 05/07/2007 | TBD | TBD Shaun Bradshaw |
Test Case Designs | 05/14/2007 | TBD | TBD Sylvia Stanfield |
Test Cases | 05/28/2007 | TBD | TBD Sylvia Stanfield |
Status Reports | Weekly | Shaun Bradshaw TBD | |
Test Logs | Ongoing during test execution | Sylvia Stanfield TBD | |
Defect Reports | Ongoing during test execution | Sylvia Stanfield, Shaun Bradshaw TBD | |
Test Summary Report | 07/17/2007 | TBD | TBD Shaun Bradshaw |
4.2 Test Schedule
The planned test schedule of the Touchstone project has an anticipated start date of 04/25/2007 and completion date of 07/17/2007. 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
...