onevcs-testing 0.1.2

[package]
name = "onevcs-testing"
# Versioned by release-plz from this repository's conventional commits, like the
# crate beside it. Its own version, because it is its own deliverable: a consumer
# pins it in `dev-dependencies` and nothing about a test provider belongs in a
# release binary.
version = "0.1.2"
edition.workspace = true
rust-version.workspace = true
license.workspace = true
authors.workspace = true
repository.workspace = true
homepage.workspace = true
description = "In-memory and file-backed implementations of onevcs's Vcs and RemoteHost interfaces, for driving a real onevcs in a test."
readme = "README.md"
keywords = ["testing", "git", "github", "vcs", "agent"]
categories = ["development-tools::testing"]
include = ["src/**/*.rs", "Cargo.toml", "README.md"]

[lib]
name = "onevcs_testing"
path = "src/lib.rs"

[dependencies]
# The interfaces these implement, and the types their states are made of. The
# version requirement is what `cargo publish` uploads — a bare path resolves to
# nothing on crates.io — and release-plz keeps it in step with the sibling.
onevcs = { version = "0.2.2", path = "../onevcs" }
serde = { workspace = true }
serde_json = { workspace = true }
# A change request's head commit and a preserved commit both need a hash-shaped
# value that is the same on every run, so a journey can assert on the state it
# seeded rather than on what a clock produced.
sha2 = { workspace = true }
# The envelope's `ts`, spelled exactly as onevcs spells it.
time = { workspace = true }
url = { workspace = true }

[dev-dependencies]
# A journey drives the same parsed command line a user types, so it parses one.
clap = { workspace = true }
tempfile = { workspace = true }

# One test binary rather than one per file, so the fixture is a module the
# journeys share rather than a file each of them compiles its own copy of.
[[test]]
name = "journeys"
path = "tests/journeys/main.rs"