#parameterized #attributes #junit #unit-testing #test

macro dev parameterized-macro

Attribute macro crate for parameterized tests

9 releases (4 stable)

2.0.0 Mar 5, 2024
1.1.0 Oct 12, 2023
1.0.1 Nov 9, 2022
1.0.0 May 2, 2022
0.1.1 Nov 14, 2019

#8 in #unit-test

Download history 557/week @ 2023-12-20 552/week @ 2023-12-27 522/week @ 2024-01-03 1224/week @ 2024-01-10 1731/week @ 2024-01-17 599/week @ 2024-01-24 480/week @ 2024-01-31 1304/week @ 2024-02-07 879/week @ 2024-02-14 681/week @ 2024-02-21 865/week @ 2024-02-28 777/week @ 2024-03-06 761/week @ 2024-03-13 791/week @ 2024-03-20 917/week @ 2024-03-27 720/week @ 2024-04-03

3,396 downloads per month
Used in 25 crates (via parameterized)

MIT/Apache

16KB
281 lines

High level overview of test case generation

An example

With this macro we generate the following code (1) from the given parameterized test definition (0):

parameterized test definition:

// 0

#[parameterized(a = {1, 2}, b = { "wanderlust", "wanderer" })]
fn my_test(a: i32, b: &str) {
    assert!(a > 0 && b.starts_with("w"))
}

generated test cases:

// 1

#[cfg(test)]
mod my_test {
    #[test]
    fn case_0() {
        let a: i32 = 1;
        let b: &str = "wanderlust";
        assert!(a > 0 && b.starts_with("w"))
    }

    #[test]
    fn case_1() {
        let a: i32 = 2;
        let b: &str = "wanderer";
        assert!(a > 0 && b.starts_with("w"))
    }
}

More examples can be found in the expand crate, and the tests.

notes:

  • The function name in (1) is the same as the module name in (0)

  • Note that arguments are not limited to primitives; they can be any expression (assuming:)

  • In a parameterized test case, the input arguments (which are expressions) specified in the attribute should evaluate to the same type as their identically named companions in the function signature.

  • Tests executed from the workspace crate should be run individually, e.g. (cargo test --package parameterized-macro --test tests individual_cases -- --exact). Otherwise, if just cargo test is used, some generated test cases will run in an incorrect context setting.

Dependencies

~1.2–1.8MB
~35K SLoC