cargo-semver-checks/.github/workflows/README.md
Mieszko Grodzicki 461983b3bb
Add test for baseline caching (#33)
* Cache test

* Baseline caching - initial work

* Add comment explaining the change of CARGO_TARGET_DIR.

* Update README.md

Co-authored-by: Predrag Gruevski <2348618+obi1kenobi@users.noreply.github.com>

* Refactor getRustcVersion and getCargoSemverChecksVersion

* Move helper functions outside RustdocCache class.

* cachePath passed in constructor

* workspaceRoot as constructor argument

* Inline getManifestDir

* Change target to semver-checks/target

* Fix missing hash-files

* Add workflow testing caching

* New line

* Add checking the updated cache

* Missing semicolon

* Bad job name in cache key

* Upload cache if its hash changes

* Test options cache-key and prefix-key

* Need to use restore-keys

* Is path a problem?

* Absolute path

* Move

* Fix restore inputs

* Verify

* Revert debug

* Rustc and semver-checks versions should not be fixed!

* debug test

* key not being a prefix

* Missing outputs

* Revert letter change in hash

* Update CI README

* TODO comments, shorter names

* Better names

* check the key

* Missing '

* Remove space

* Missing outputs

* Remove hash check

---------

Co-authored-by: Predrag Gruevski <2348618+obi1kenobi@users.noreply.github.com>

* Remove inconsistent newlines from workflows README

---------

Co-authored-by: Predrag Gruevski <2348618+obi1kenobi@users.noreply.github.com>
2023-04-07 10:54:46 -04:00

758 B

The testing workflow is divided into several parts:

  • test-action.yml, which contains simple, general integration tests of the action that should be run on each platform

and the following ones run on ubuntu-latest:

  • test-build.yml containing source-related checks: linters, formatters and verifying whether the sources match dist/ directory,
  • test-inputs.yml containing specific integration tests checking whether the action inputs are processed properly,
  • test-cache.yml focusing on veryfing whether the baseline rustdoc is cached correctly.

setup-test-workspace is a helper action that creates a workspace containing two crates: the test fork of ref_slice and a dummy crate that has no matching baseline version on crates.io.