Test data

[BCerki]

Prep for #2222 . It's really hard to test reg2 db changes when we still have to keep the reg1 e2e tests running, and having both reg1 and reg2 stuff in the app is v confusing for testers and POs.

This PR:

• make a copy of the existing fixture files in mock/v1
• creates a separate load fixture command for reg1 to pull from the mock/v1 folder
• uses this new command in the v1 test-setup endpoint. This endpoint is called to set up e2e tests (definitely) and the data in the dev env (I think, right @dleard? I see it called here: cas-registration/helm/cas-registration/templates/backend/job/load-dev-data.yaml)
• changes Operator 1 to Alpha Industries in reg2 mock data only to confirm that separate data can coexist (card Improve reg2 mock data #2627 handling improving the reg2 data)
• all the existing make commands refer to the original load fixture command, so no changes needed. All the model test fixtures also refer to the original directory so also no changes needed
• happo is flake

[andrea-williams]

I notice this is in v1 directory, but facilities are only relevant to Reg 2. Is this an oopsie?

[BCerki]

Yup! There's a few others I can delete too, thanks!

[BCerki]

This might make reg1 e2e run faster too 👀

[andrea-williams]

do we need to have the "Transferred", "Closed", "Temporarily Shutdown", "Registered" statuses for v1?

[BCerki]

The reg1 e2e tests do appear to be looking for those reg2 statuses, because CI fails when I take them out (and the code snippet below is maybe relevant?). I'll see if I can get @shon-button 's help figuring out where the failing assertions are, but if it's not straightforward, are you okay with me leaving these statuses in for this PR, and I'll add an AC about getting rid of them to #2627 ?

In /home/briannacerkiewicz/cas-registration/bciers/apps/registration1/e2e/poms/operations.ts:

expectedValues = [
              OperationStatus.PENDING,
              OperationStatus.APPROVED,
              OperationStatus.DECLINED,
              OperationStatus.CHANGES_REQUESTED,
              OperationStatus.REGISTERED,
              // Below values are not possible in Registration1
              OperationStatus.CLOSED,
              OperationStatus.TEMPORARILY_SHUTDOWN,
              OperationStatus.TRANSFERRED,

[andrea-williams]

I'm a bit confused by the naming conventions - is loadfixtures_v1 for Reg1 and loadfixtures for Reg2?

[BCerki]

Yes, I'll make a comment and add some docs. This is to match how we've done the nx apps and the endpoints (so when we delete reg1 we're just left with reg instead of reg2, v2, etc.)

[andrea-williams]

Approving. Thanks for doing this Bri - it will help out a lot of people! :D