Create new Committees for Testers for UAT #3

[exalate-issue-sync[bot]]

Purpose

Create a new committees on these two environments (STAGE & PROD) for the following users that most approximates an actual Form 3X committee.

Please add this (and all the other committee detail data) to the s3 bucket so it can be updated as needed.

QA Notes

Screenshots of mock data pulled from API showing mock data used in committee banner.

DEV Notes

Download the current mock_committee_data.json from the s3 bucket and modify it to add the new committee accounts with your email address so you can create the accounts through the UI. Push this back to s3 and then run the load_committee_data script with the --s3 flag. Next, you will need to login through the UI and create the accounts in the select committee screen. Next, you will need to update mock_committee_data.json with the fake email address for the new accounts and re-push it to s3. Next, you will need to run the load_committee_data script again. Finally, verify that the committee account details in the UI contain the fake email address and all other expected info.

See here for details on mock_openfec:

https://github.com/fecgov/fecfile-web-api/blob/develop/django-backend/fecfiler/mock_openfec/README.md

Do after deploy in:

• [x] STAGE
• [x] PROD

Tasks

• Move the mocked committee data with your email address for new committee accounts into an s3 bucket
• Run the load_committee_data script with --s3 flag
• Create the new new committee accounts in the UI select committee accounts screen
• modify the mocked committee data file to replace your email address with the fake email address for the new committee accounts.
• re-push the mocked committee data file to s3 and run the load_committee_data script again with the --s3 flag.
• Verify that the committee account details in the UI contain the fake email address and all other expected info.

Create a new committee in duplicate

• [x] created on STAGE
• [x] created on PROD
• [ ] Please associate committees with their http://Login.gov email

Ryan already created the committee with EFO on test please verify the information below matches the information you pull

• [x] FEC ID: C00101303
• [x] Committee Name: The Leadership PAC
• [x] Filing Frequency: Monthly
• [x] Status: Active (Hard code if needed)
• [x] Committee Type in Application: PAC - Nonqualified - Leadership PAC
• [x] Committee Designation in Database: D - Leadership PAC
• [x] Committee Type in Database: N - Non-Qualified Non-Party

Design

null

FECFILE-1422

[MitchellTCG]

@dheitzer can we push this to QA?

[mjtravers]

New user accounts verified by Ryan and new users confirmed they were able to log into their new committees. Sending ticket to QA.

[WiseQA]

No QA review needed for this ticket. DEV verified new user accounts and ability to login to the new committees.

Moved to Stage Ready.

[exalate-issue-sync[bot]]

Aurelia Khorsand commented: Sprint accepted 6/18/2024 during Sprint Review.