testing-conventions 0.0.22

Enforce testing conventions in libraries (Python, TypeScript, and Rust).
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

//! E2E tests for the workflow guard (#92): drive the built CLI binary against the
//! fixture workflows and assert the exit code. The guard: a `testing-conventions`
//! invocation in a workflow must name a subcommand the binary still exposes, so a
//! rename can't strand the `@v0` consumption path.
//!
//! These start red — the skeleton's `workflow` command reports nothing, so the red
//! fixture exits `0` instead of `1` — and go green once detection lands.

use std::path::PathBuf;
use std::process::Command;

fn fixture(name: &str) -> PathBuf {
    PathBuf::from(env!("CARGO_MANIFEST_DIR"))
        .join("tests/fixtures/workflow")
        .join(name)
}

/// Exit code of `testing-conventions workflow <fixture>`.
fn workflow_exit(name: &str) -> i32 {
    Command::new(env!("CARGO_BIN_EXE_testing-conventions"))
        .arg("workflow")
        .arg(fixture(name))
        .status()
        .expect("the built binary should run")
        .code()
        .expect("the process should exit with a code")
}

#[test]
fn red_workflow_exits_nonzero() {
    assert_eq!(workflow_exit("red"), 1);
}

#[test]
fn clean_workflow_exits_zero() {
    assert_eq!(workflow_exit("clean"), 0);
}