PoC: Add system test spanning multiple domains (Create Metering Point process)

[prtandrup]

PoC: System test with a business process spanning multiple domains. Business Process: Create metering point Domains: Metering Point, Charges, MessageHub (and APIM)

What: Run 'Create metering point' process as a system test; initiated by an incoming request and verified by multiple outgoing messages

Test flow: Scope: Grid Access Provider only

• Submit Create MP request
• Peek & Dequeue confirmation
• Peek & Dequeue master data (needed?)
• Peek & Dequeue charge link
• Get Metering Point through BFF
• Get Charge Links through BFF (needed?)

Environment: T-001

When / Trigger: Nightly (somewhere between 00:00-04:00) / Manually

Acceptance criteria:

• [ ] The system test is executed by a scheduler
• [ ] The system test can be triggered manually
• [ ] Given the system test has failed, when I check the 'Alert channel for the T-environment', then I see a "system test failed" entry with a link to the build log.
• [ ] System test is documented

Tasks:

• [ ] Folder structure & GitHub workflow
• [ ] Port existing test code from Charges domain (for authentication + Message Hub peek & dequeue interaction)
• [ ] Find the correct market participant to use for system test in T-001
• [ ] Write the 'create metering point process' test
• [ ] Document the test setup (what, when & how)
• [ ] If system test fails; report failing system test in "T-001 alert channel" in teams

Authors: Daniel P, and Dan and I.

[kariws]

Aftalt demo af Volts domænetest og systemtest torsdag i uge 37.