Setup load testing committee account on DEV

[exalate-issue-sync[bot]]

When running load tests against DEV using Locust, we will be using a single committee account to run tests against. This committee account will be cleaned out of all transactions and reports after each load test.

Tasks

1. Create or declare an existing committee account on DEV to be used exclusively for load testing.
2. Add all developer login accounts to that committee account.

QA Notes

Screenshot of user list for commitee account provided for QA.

DEV Notes

null

Design

null

FECFILE-1538

[exalate-issue-sync[bot]]

Completed the following in DV:

• registered a new F1 in test efo for new committee LOAD_TEST_COMMITTEE_NAME1
• added new committee to s3/redis committee data
• created new committee
• added all devs to this account

[exalate-issue-sync[bot]]

David Heitzer commented: for QA:

!image-20240828-180547.png|width=839,height=689,alt="image-20240828-180547.png"! See image in Jira