Hello Team,

Here's update to Load Performance Testing with milestones and plans proposals. Topics are listed
form highest priority to lower. If there's any malposition in priorities, please let's discuss about it.

- S1A Web Services scenarios are integrated in Main LP Test script

Tests are performed in two ways:

- Web Services scenarios enabled only

- All scenarios enabled

Comparison results table is attached. One "all scenarios" test has unexpectedly returned higher error
rate on WS scenarios. All WS scenarios are updated and local Summary Results component is removed
from scenarios used for Smoke, Standard and Extended test. Summary report for functional testing
remained.

This make us ready for new build application (4.15 build 9 or later) and database restore. As soon as
we get new build ready we can perform weekly tests. This task will be performed by Stevan and Bojan.

Passed test for new build will initiate update for Submission scenarios. Submission scenarios will be
multiplied where file upload occurs and we'll integrate different file type/size in every scenario.

- S1M Scenario recording

Since Web Services are scripted for S1A it's presumable that scripting for S1M Web Services testing
wouldn't take too much time. Main prerequisites for S1M WS scripting is getting access parameters
for PLANO S1M database and hardcoded Data Sets that are made from query posted to database.

S1M Web Services scenarios will be, as in S1A case - coded in standalone local JMeter script, and lately
translated to Test Fragment usable in main test script. After successfully performed S1M WS test we
should discuss about time and team members engagement for S1M scenarios recording.

(Proposed completion time - 20 hours)

- Script crossover / AWS Spin-up

All recorded scenarios should be applicable for crossover testing using Eagan/Plano/AWS database
environments. AWS access should be performed using Bastion SSH Host, and as soon as we gain access
to it - migration to new AWS server can be initiated. As we discussed earlier this year, migration could
be performed in three levels of effort - High Effort Level / Low Effort Level / No effort Level.

It is most likely that Main LP test script could be executed using new environment with very low effort
level. It requires AWS access credentials and procedures, and also - some time spent on integration to
verify that statement.

(Proposed completion time - 40 hours, less or more… LOE will be updated)

- DynaTrace / Kibana log services

As far as we know, S1 team aims to connect existence performance results with Kibana results logging
platform. Kibana is completely new platform for us, so - we expect some hints and directions for
connecting to this reporting environment. Also, refer us to the key person roles that could be helpful
in preforming this task. This part of test integration must involve presence of Stevan Bekvalac and
Bojan Ritoc.
(Proposed completion time: Couldn't be estimated yet)

- DB connection / Live Query Data Sets

Web Service testing is performed with hard-coded Data Sets and it could be considered as a certain
vulnerability of main test script scenario. Proper solution for database query which will gather data
for live Data Set construction would make WS test more flexible and reliable. Amitesh Chandra is
addressed as Person of knowledge for integrating JMeter DB Query solution. As soon as tasks with
higher priority are performed, Mr. Chandra will be contacted for hits and directions regarding that.

(Proposed completion time: Couldn't be estimated yet)

- Documentation update

Maintenance and update of Scenarios scripts and Main JMeter script brought us to the point where
all documentation regarding that should be updated with new information gathered from performed
tests.

(Proposed completion time: 40 hours)

- Training videos and SOP documentation

After completion of al tasks with higher priority, documentation accompanied with recorded tutorial-
videos should be recorded and written.

(Proposed completion time: Couldn't be estimated yet)

Weekly time budget for Stevan's Load Performance engagement is 16 hours. I will take liberty to
involve him on every daily task to support testing. If Stevan's tasks couldn't permit full engagement
for given budget - Bojan will take over.

Please, review this update and feel free to comment and correct any given topic.

Thank you.