Page History
...
Step | Name | Description |
---|---|---|
1 | Login | The user logs in with a username and password. |
2 | Start project | Start the application and display the Welcome screen |
3 | Open ATMs section | Switch to the Find Local ATMs page |
4 | Search ATMs | Creates 500 instances using the AQ_CsvConnectivityService and an external CSV file, then switches to the Confirm ATMs Found page. |
5 | Display Search Results | Opens the Display ATMs page where the previously created instances are displayed in an AQ_InstanceList with page size 20. |
6 | Go to the loan offers page | Navigates to the Loan Offers page. |
7 | Apply for prime offer | Updates an instance through the ‘AQ_InstanceUpdate’ service and navigates to the Loan Form is brought inpage. |
8 | Open calculator | Opens the Borrowing Calculator page |
9 | Fill in fields (1) | Fills in the available page fields. Other conditional fields are presented to the user as a result of this action. |
10 | Fill in fields (2) | Fills in the newly available page fields. New fields are displayed as a result of this action. |
11 | Fill in fields (3) | Fills in the newly available fields on the page. |
12 | Calculate | Updates 3 instances belonging to separate entities using the ‘AQ_InstanceUpdate’ service and displays the calculation results to the user. |
13 | Go to first page | Returns to the Welcome page. |
14 | Open the loan offers page | Navigates to the Loan Offers page. |
15 | Apply for a fixed rate | Updates an instance through the ‘AQ_InstanceUpdate’ service and navigates to the Loan Form page |
16 | Fill in fields (4) | Fills in the available fields on the page. Some fields are refresh fields and have validations. |
17 | Fill in fields (5) | Fills in the available fields on the page. Some fields are refresh fields and have validations. |
18 | Fill in fields (6) | Fills in the available fields on the page. Some fields are refresh fields and have validations. |
19 | Continue | Navigates to the Personal Information page |
20 | Fill in personal form | Fill in all fields and navigates to the Document Upload page. |
21 | Upload file | Uploads a file to certify the users identity. As the upload is successful an ‘AQ_FileDownload’ container is generated on the page. |
22 | Download file | Downloads the previously uploaded file. |
23 | Submit request | Navigates to the Confirmation page. |
24 | Go to the loan offers page | Navigates to the Loan Offers page. |
25 | Log out | The user logs out. |
Application Interface
Screen | Content |
---|---|
Welcome | The welcome screen with 4 inline containers, 3 text items and 2 buttons. |
Find Local ATMs | A page with 2 inline containers, a text item and 2 buttons. |
Confirm ATMs Found | A page with 2 inline containers, a text item and 2 buttons. |
Display ATMs | Displays the nearby ATMs using an AQ_InstanceList with page size 20. Also contains 2 inline contains and 2 buttons. |
Loan Offers | The page contains dozens of containers and text items, each of them having presentation or content styles assigned. |
Borrowing Calculator | Contains 7 inline containers, 10 fields and 2 buttons. 5 fields are refresh fields, additional fields become available depending on the values entered into the refresh fields, using inline containers with preconditions. |
Loan Form | Contains 3 inline contains, 1 texxt item, 3 buttons and 8 fields. 3 fields are refresh fields with validations. |
Personal Information | Contains 2 inline containers, 2 buttons and 16 fields. 4 fields are refresh fields. 2 fields have preconditions and are shown or hidden based on the information entered in the refresh fields. |
Document Upload | Contains 4 inline containers, 2 text items, 1 button, an AQ_File_Upload container and intially zero AQ_File_Download containers. When a file is uploaded, a new AQ_File_Download container is displayed, using a repeat expression. |
Confirmation | Contains a logout text item, a text item confirming the completion of the loan request and a button which leads back to the Loan Offers page. |
3 Simulating application usage
The simulation which is executed on the application during the performance test scenario depends on two variables:
- the user load that must be simulated on the system during the test
- the total duration of the test execution
The user load is a constant number of users (threads), with a rampup time of 5 minutes. The user load is different based on the session store type being used:
- memory session store: 450 users
- redis session store: 800 users
After the 5 minute ramp-up, the load is sustained for one hour.TBD
4 Test environment
For the performance tests a typical hardware configuration is used that consists of two separate servers for the Runtime and JMeter. The specification of the test environment is described in the test reports.
...