jacderida/cargo-nextest
Perform a test run using cargo nextest and upload the test report as an artifact. This action is going to work under the assumption that the caller has already installed a Rust toolchain, as the use case for it is alongside other uses of Cargo/Rust.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| bin | Use to specify running tests in a certain binary. | no | — |
| features | Space separated list of Cargo features to enable. | no | — |
| filters | Space separated list of particular test names to run. If not supplied, all tests will run. | no | — |
| junit-path | Value of the Junit path attribute used in the nextest profile, e.g., junit.xml. | yes | — |
| package | Name of a crate to test. This is useful if your repository is a workspace. | no | — |
| profile | Name of the nextest profile to use. | yes | — |
| release | Test against code built in release mode. | no | false |
| retries | The number of retries to use for failed tests. If not supplied, this will default to the value specified in the profile. | no | — |
| run-ignored | Used to run ignored tests when that is desirable. | no | false |
| test-run-name | The name to use for the test run, e.g. unit-test-ubuntu-latest. This will be the name of the artifact with the test reports. | yes | — |
| test-threads | The number of test threads to be used. If not supplied, the nextest default will be used, which is the number of logical CPUs. | no | — |
Outputs
no outputs