Undefined Use Pact for contract testing between HAC-dev and other services. The first steps may be like this:
- implement POC
- HAS simple scenario of application creation
- HAC-dev sends a request for app creation and HAS returns 200
- try a more complex scenario
- pre-create an app with two components on HAS side
- components should be one from GH and one Quay
- use State for this
- HAC-dev will send request to gett an app with components
- pre-create an app with two components on HAS side
- incorporate this as part of a job for PR check tests
- create Pact broker for storing the contracts
- find out the best way for versoining pacts
- start on HAC-dev side
- create a check on HAS side
- investigate how to use that as a check for pushing to staging/production
- try to use 'can-i-deploy' for those purposes
Once we have some test running well, pipelines setup and checks working, we can add more tests from HAS API and add more components (SPI, etc.).
1.
|
DOD: Training materials supplied to Support/SRE |
|
To Do | 
|
Unassigned |
2.
|
DOD: Docs verified by QE |
|
To Do |
|
Unassigned |
3.
|
DOD: Docs completed and merged |
|
To Do |
|
Unassigned |
4.
|
DOD: All known issues captured and blockers resolved |
|
To Do |
|
Unassigned |
5.
|
DOD: Code merged for regular build/release testing in the HAC Common CI/CD framework |
|
To Do |
|
Unassigned |
6.
|
DOD: CI runs successfully with test automation |
|
To Do |
|
Unassigned |
7.
|
DOD: Automated/Integrated tests complete |
|
To Do |
|
Unassigned |
8.
|
DOD: Architectural artifacts completed, reviewed and stored |
|
To Do |
|
Unassigned |
9.
|
DOD: Product Manager and UX signed off on solution |
|
To Do |
|
Unassigned |
10.
|
DOD: Acceptance criteria related to this Epic has been identified and met |
|
To Do |
|
Unassigned |
