allure-test-macros 1.0.2

Procedural macros for Allure Rust test and step instrumentation.
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
38
39
40

# allure-test-macros

`allure-test-macros` contains the procedural macros used by the workspace.
In most cases you should depend on `allure-cargotest` instead, because it re-exports these
macros together with the runtime integration.

## Recommended usage

Add the higher-level crate:

```bash
cargo add allure-cargotest --dev
```

Then use the re-exported macros:

```rust
use allure_cargotest::{allure_test, step};

#[step(name = "Open login page")]
fn open_login_page() {}

#[allure_test(name = "Login works", id = "AUTH-1")]
#[test]
fn login_works() {
    open_login_page();
}
```

## What the macros do

- `#[allure_test]` wraps a `#[test]` function with Allure lifecycle setup and teardown.
- `#[step]` records a function call as an Allure step.
- Optional macro arguments let you override the displayed test or step name.

## Notes

- `#[allure_test]` currently supports synchronous test functions that return `()`.
- The macro uses `ALLURE_RESULTS_DIR` when set, otherwise `target/allure-results`.
- This crate is intended as an implementation crate for proc macros.