The self dogfooding of this workflow is good, and we have https://github.com/ProdigySim/acw-testing to test the e2e consumer scenario, but this is not really convenient or automated.
How can we properly test this workflow? It relies on behavior of both github actions and git.
Brainstorming:
- Use act to simulate the workflow on local / with a local repository
- Allow a workflow parameter to customize directory target or repo checkout target
- Create and destroy an entire separate github repo to test e2e
- Break workflow into substeps as actions and unit test steps
The self dogfooding of this workflow is good, and we have https://github.com/ProdigySim/acw-testing to test the e2e consumer scenario, but this is not really convenient or automated.
How can we properly test this workflow? It relies on behavior of both github actions and git.
Brainstorming: