= BluePrint: Load Test =
[[TOC]]

The tests are located in {{{modules/tests/load}}}

==  Load Test Parameters ==
Load Tests can be developed for different 
=== Template === 
Which template is being tested
 
=== Number of Users === 
The number of simultaneous users who will be using the 

=== Sessions === 
Which sessions are bing tested and how many of each
* 20% create_staff
* 40% search_staff
* 40% report_staff

=== Number of Records === 
The number of additional records which should be created prior to running the load tests to test the response for a large number of records.

=== Server Being Testing ===
This should be defined in the Use Case file, but there should also be deployment setting which can be an override for ALL use cases.

==  Load Test Files ==

=== Use Cases ===
{{{modules/tests/use_cases/}}}[[BR]]
Load tests can be run for a number of different use cases. Each use case will specify the exact parameters for the load test

=== Template Helper Files ===
{{{modules/tests/helpers/templates/}}}[[BR]]
These will be template specific files that record the template specific static files to be downloaded on each page.

=== Session Files ===
{{{modules/tests/sessions/}}}[[BR]]
These are the different sessions being tested.

Example
* ??

=== Helper Files ===
{{{modules/tests/helpers/}}}[[BR]]
Requests which will be common to many tests. [[BR]]
These can be reused in multiple sessions.[[BR]]
Example:
* login requests will be common to all tests which require login

=== Data Files ===
{{{modules/tests/load/data}}}
Scripts to create additional records to test the load with a large number of records.
This will both add records directly to the database to test the server with a large number of records as well as create a CSV file of records which can be added by load tests.

== Load Test Process ==

=== 1. Config Load Test ===

=== 2. Create Records ===

=== 3. Run Load Tests ===

=== 4. Report Results ===

----
BluePrint