You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, if we want to run a test locally, we need to look at the GitHub Actions to figure out how to run it and reproduce the steps in several commands/scripts.
It would be easier if we had make commands for running each test and the GitHub Actions called those make commands instead.
Notes
Workflows need to be updated to use the new make targets
make commands for running tests should not install any tools. In case of having a tool as a pre-requirement, we can have a specific make command for that.
Some stuff will likely remain on GitHub Actions, like creating a kind cluster, for example. We can also have a make command to create a kind cluster, but that would be used only for developers to run tests locally. It wouldn't be called by GitHub Actions.
Labels
/area testing
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered:
Chore description
Right now, if we want to run a test locally, we need to look at the GitHub Actions to figure out how to run it and reproduce the steps in several commands/scripts.
It would be easier if we had
make
commands for running each test and the GitHub Actions called thosemake
commands instead.Notes
make
targetsmake
commands for running tests should not install any tools. In case of having a tool as a pre-requirement, we can have a specificmake
command for that.make
command to create a kind cluster, but that would be used only for developers to run tests locally. It wouldn't be called by GitHub Actions.Labels
/area testing
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered: