...
Scripts will be designed to model various user interactions with the system. While most of the user interactions will be scripted, some may be omitted according to the 80/20 rule and/or any time constraints which may exist.
3.2 Tools
The tools we will employ are yet to be determined. A proof of concept (PoC) is under way on a performance testing tool. If it is acceptable to MIT then this tool will be identified here. Otherwise further PoCs may need to be conducted until a satisfactory tool is identified and accepted by MIT.
The following tools will be used as part of the overall Touchstone testing effort:
Tool | Purpose | Used By |
Atlassian Jira | Web-based defect tracking system accessed by http://mv.ezproxy.com.ezproxyberklee.flo.org/jira | Touchstone Project Team (MIT & Questcon) |
| Performance testing / load generation tool |
|
3.3 Environmental Needs
We will need the following:
...
The following scripts will be used during the performance testing effort.
When the design steps have been provided by MIT all of the to be determined (TBD) values will be replaced with the actual values.
4.1 CAMS Account Creation
...
A performance test is designed to benchmark the system under test under a realistic load scenario that mimics what we anticipate real world usage will be at its peak.
References to non-functional requirements marked as TBD will be updated once the non-functional requirements are provided by MIT.
5.1.1 IdPi Only
The objective of this scenario is to benchmark just the internal IDP.
...
7.0 Non-functional Requirements
MIT has not yet provided the non-functional Requirements. The link below will be updated if a web page is created to house them, otherwise they will be specified here.
Touchstone Non-functional Requirements
...