Automate zilla
develop-SNAPSHOT
acceptance tests for zilla-examples
scenarios
#1434
Open
3 of 36 tasks
Describe the desired outcome from the user's perspective
As a
zilla
developer, I want to have confidence that my changes have no negative impact onzilla-examples
scenarios.Acceptance criteria
zilla-examples
scenario is automated via GitHub Actions, following the steps in each READMEdevelop-SNAPSHOT
version ofzilla
is used for automated testing by defaultdevelop-SNAPSHOT
build ofzilla
is created and cached via GitHub Actions as neededAdditional context
See potentially helpful
kind
tool for k8s automation.Running GH actions can be executed in a container. The container needed for the GH action can be pulled locally to test any action steps.
sparse-checkout
can only clone certain folders or patterns of folders.Export results to the $GITHUB_OUTPUT var.
Use path-specific action triggers and global env vars to make jobs and tasks more generic.
Tasks
develop
and run example tests #1263openapi.proxy
scenario acceptance tests zilla-examples#124tls.echo
scenario acceptance tests zilla-examples#125The text was updated successfully, but these errors were encountered: