...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
This document includes below details:
1. Performance Scripts: The location of the scripts in eGov GIT
2. Scope of the scripts: what scenarios it will cover.
3. Test Reports: The location of the test reports that is sent so far in eGov folders
4. The current status that we are in. I.e., the current configuration, latest report and issues that we have.
5. What are the resolutions and next steps for the same?
6. Issues and Resolutions
5. Test Data setup and Tools Used
Performance Test Scripts:
All the Performance Test scripts, and Test data will be shared in the Google drive and provide the access to all EGov Users.
https://drive.google.com/drive/folders/1kuF0kR8qD6A96dq30qErYnaStP_K76-q?usp=sharing
GIT HUB Link for Performance Test scripts, Test Reports and Test Data
https://github.com/egovernments/test-automation
Test data files are also saved in the same path.
Scope of the scripts:
EGov JMeter scripts cover the below Functionalities in MGramSeva Application and IFIX API’s.
Total 10 Web UI Scripts for MGramSeva and 3 API Scripts for IFIX
S No | Scenario Name |
1 | Create Consumer Metered |
2 | Create Consumer Non-Metered |
3 | Create Consumer Zero Arrears |
4 | Collect Payment Metered |
5 | Collect Payment Non-Metered |
6 | Download Receipt Metered |
7 | Download Receipt Non-Metered |
8 | Generate Demand |
9 | Add Expense Paid |
10 | Add Expense Un-Paid |
11 | Fiscal Event Push (API) |
12 | Bulk Fiscal (API) |
13 | IFIX Bulk Adaptor (API) |
Test Reports:
Performance Test reports are shared in the google drive and as well in the GIT HUB.
https://drive.google.com/drive/folders/1kuF0kR8qD6A96dq30qErYnaStP_K76-q?usp=sharing
GITHUB Link
https://github.com/egovernments/test-automation
Performance Testing Status:
...
We have reported the same across the team in the Report email.
Issues and Resolutions:
Initially we have executed the Performance Test with 30 users and observed 503 Service Temporarily Unavailable Error. Frontend team has increased the POD’s count to 2.
In the second round of Performance Testing, we have increased the users and at 100 users we are observing 503 error.
We are observing CPU and Memory Utilization high along with 503 Service Temporarily Unavailable Error during the Test run.
...
For reporting we have used HTML format report and used excel report for transaction response time values.
Test Data Set-up:
Before starting the test, We need to create the 500 consumers for Metered, Non Metered and Zero arrears flows.
Change the Parameter values in the script before running the test.
Also need to use the freshly created consumers for collect payment Metered and Non-Metered scripts.
Need to change the mobile number parameter in the Add Expenses Paid and Unpaid scripts, change the values in the .csv file which is added to the Parameter data set.
In MGramSeva application Mobile number field should be unique for all the scripts.
Script Name | Parameters Used |
Create Consumer Metered | Username, ConsumerNumber_Metered |
Create Consumer Non-Metered | Username, ConsumerNumber_Non_Metered |
Create Consumer Zero Arrears | Username, ConsumerNumber_Non_Metered |
Collect Payment Metered | Username, ConsumerNumber_Metered |
Collect Payment Non-Metered | Username, ConsumerNumber_Non_Metered |
Download Receipt Metered | Username, ConsumerNumber_Metered |
Download Receipt Non-Metered | Username, ConsumerNumber_Non_Metered |
Add Expense Paid | Username, PaidAddExpMobNo |
Add Expense Un-Paid | Username, UnPaidAddExpMobNo |