PackageTrack
Sign in Get early access

expect-test

Minimalistic snapshot testing library

1.5.1 35M downloads/mo #1532 most downloaded on crates.io rust-analyzer/expect-test

What this package is like to depend on

Last release 2 years ago

no release in 18 months

Release timing varies

gaps range from 2 weeks to 13 months

Most releases are documented

notes for 9 of 13 stable releases

Nothing withdrawn

no release was ever pulled

6 years old

14 releases · first in 2020

0 releases in the last 12 months

see the full history below

Release timeline

14 releases · Aug 2020 to Dec 2024
2021 2022 2023 2024 2025 2026
Release Pre-release

Releases

latest 14
  1. 1.5.1 21 Dec 2024
    Release notes
    • Documentation improvements
    Open source →
  2. 1.5.0 02 Apr 2024
    Release notes
    • Make the data from an ExpectFile accessible ([#43])
    Open source →
  3. 1.4.1 28 Feb 2023
    Release notes

    Merge pull request #36 from knrafto/fg-colors

    Open source →
    Release notes
    • Use foreground colors instead of background colors to highlight diffs ([#36])
    Open source →
  4. 1.4.0 19 Jul 2022
    Release notes

    ⬆️ 1.4.0 (with changelog entry)

    Open source →
    Release notes
    • Prefer CARGO_WORKSPACE_DIR if set, use heuristic as fallback to find cargo workspace ([#34])
    Open source →
  5. 1.3.0 25 May 2022
    Release notes
    • Add data() getter to Expect ([#31])
    • Support single delimiter version of expect![] ([#27])
    • Allow users to rebind expect! ([#26])
    Open source →
  6. 1.2.2 25 Dec 2021
    Release notes

    25: make it a bit more production ready r=matklad a=matklad

    Co-authored-by: Aleksey Kladov [email protected]

    Open source →
    Release notes
    • Parse string literals to find their length ([#23])
    • Do not use fs::canonicalize.
    Open source →
  7. 1.2.1 30 Nov 2021
    Release notes

    17: Respect user provided absolute path r=matklad a=mvtec-bergdolll

    When the environment variable CARGO_MANIFEST_DIR is not present as is the default when opening a workspace project in vs code and running the tests. expect-test panics.

    The problem can be reproduced with this minimal project https://github.com/mvtec-bergdolll/expect-test-repro-proj/tree/main. Open it in vs code and run the integration tests. They panic. However running them from the shell does not panic. That's unfortunate.

    As user trying to debug this I was confused why it failed even when providing an absolute path.

    This change includes:

    • Do not query CARGO_MANIFEST_DIR if the user already provided an absolute path when calculating an absolute path
    • Better error message when CARGO_MANIFEST_DIR is not present

    I'm not sure how to easily test this so I've not added automated testing.

    Co-authored-by: Lukas Bergdoll [email protected]

    Open source →
    Release notes
    • No changelog until this point :-(
    Open source →
  8. 1.2.0-pre.1 09 Oct 2021 pre-release
    Release notes

    16: allow disabling automatic indentation on update r=matklad a=matklad

    closes #10

    bors r+

    Co-authored-by: Aleksey Kladov [email protected]

    Open source →
  9. 1.1.0 01 Jan 2021
    Release notes

    11: Use dissimilar for diffs instead of difference r=Jesse-Bakker a=Jesse-Bakker

    As discussed with @matklad in rust-lang/rust-analyzer#7106.

    Before:

    After:

    Used background instead of foreground colours because I think the diff boundaries are clearer, but I'm not married to that change ;)

    Co-authored-by: Jesse Bakker [email protected]

    Open source →
  10. 1.0.2 07 Dec 2020
    Release notes

    9: Fix diff direction r=matklad a=lnicola

    Co-authored-by: Laurențiu Nicola [email protected]

    Open source →
  11. 1.0.1 31 Aug 2020

    Nothing published for this version

  12. 1.0.0 28 Aug 2020

    Nothing published for this version

  13. 0.1.0 21 Aug 2020

    Nothing published for this version

  14. 0.0.1 20 Aug 2020

    Nothing published for this version

Every package, every release, already written down.

The archive is open and free. Watching your own project is what we are building next.

Browse the archive