cargo/crates/cargo-test-support
bors 4b681c7338 Auto merge of #13980 - epage:compare, r=hi-rustin
refactor: Transition direct assertions from cargo-test-support to snapbox

### What does this PR try to resolve?

Cargo has a bespoke testing framework for functional tests
- Extra stuff for us to maintain
- Don't leverage benefits from contributions related to other projects
- Less incentive to be thoroughly documented

UI tests are written using snapbox.  The latest release of snapbox (#13963) was geared at supporting cargo's needs in the hope that we can consolidate on testing frameworks.

Besides having a single set of semantics, benefits we'd gain include
- Updating of test snapshots
- Fancier redacting of test output (e.g. #13973)

This is the first incremental step in this direction.  This replaces direct assertions with snapbox assertions.  This still leaves all of the CLI output assertions. These will be done incrementally.

### How should we test and review this PR?

### Additional information
2024-06-02 14:48:01 +00:00
..
containers chore(deps): update alpine docker tag to v3.20 2024-06-01 00:52:26 +00:00
src refactor: Port from matches_contains to assert_e2e 2024-05-29 14:08:10 -05:00
build.rs style(test): Remove check-cfg warning 2024-05-06 16:52:29 +02:00
Cargo.toml feat(test): Auto-redact elapsed time 2024-05-27 21:27:25 -05:00
LICENSE-APACHE Chore(cargo-test-*): Add license file links 2024-03-26 11:09:32 +01:00
LICENSE-MIT Chore(cargo-test-*): Add license file links 2024-03-26 11:09:32 +01:00
README.md Docs(crates/cargo-test-*): Add external usage warning 2024-03-26 11:17:34 +01:00

WARNING: You might not want to use this outside of Cargo.

  • This is designed for testing Cargo itself. Use at your own risk.
  • No guarantee on any stability across versions.
  • No feature request would be accepted unless proved useful for testing Cargo.