<@UQX3ZNU12> are you generally interested in the i...

# github-workflows-kt

[Nikky]

@Piotr Krzemiński are you generally interested in the idea of using snapsots built on github actions (or locally on your machine) to run integration tests from scripts ?

as far as i can tell all integration tests are running on the last stable release of the library right now and cannot test newly added code

my rough idea would be to have one workflow to do publishToMavenLocal and zip up ~/.m2/respository/.... turn it into a artifact on github,
add a workflow dependency/trigger and a step to the integration tests that loads and unzips it into place before executing the scripts

[Piotr Krzemiński]

Currently the closest thing to the integration tests for the version of the library corresponding to a given commit are handled by https://github.com/typesafegithub/github-workflows-kt/blob/main/github-workflows-kt/src/test/kotlin/io/github/typesafegithub/workflows/RunOnGitHubTest.kt. This test both generates the YAML and ensures that the YAML is in sync with the test. So it's not like only the released version is tested. The biggest con is that it doesn't actually use Kotlin scripting, which may not test certain script-specific behaviors and features. We can think of using Maven local to rewrite the integration tests, yes

[Piotr Krzemiński]

Some thoughts on the implementation:
• the artifacts would have to be keyed by commit hash
• The Kotlin Script consuming the artifact would have to refer to it by the currency project version, so it's another place to update the version when releasing, but it's bearable
• we probably need to add an extra step to the consistency job to load the artifact to .m2 prior to compiling the script. This step would exist only for the purpose of the integration tests, so we could add a generic extension point to the library to customize the consistency check job

[Nikky]

I reached pretty much the same conclusions