Merged
Conversation
Contributor
Reviewer's GuideThis PR runs File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Contributor
Summary by CodeRabbit
WalkthroughApply editorial and formatting refinements to several Markdown documentation files. Adjust line wrapping, spacing, punctuation, and minor phrasing for improved readability and consistency. Do not alter any technical content, logic, or described procedures in the affected documents. Changes
Possibly related PRs
Poem
✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![codescene-delta-analysis[bot]](https://avatars.githubusercontent.com/in/53921?s=60&v=4){kind=small}
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 8
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (5)
AGENTS.md(2 hunks)docs/netsuke-design.md(39 hunks)docs/roadmap.md(1 hunks)docs/rust-testing-with-rstest-fixtures.md(33 hunks)docs/snapshot-testing-in-netsuke-using-insta.md(14 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
docs/**/*.md
Instructions used from:
Sources:
📄 CodeRabbit Inference Engine
- AGENTS.md
**/*.md
Instructions used from:
Sources:
📄 CodeRabbit Inference Engine
- AGENTS.md
⚙️ CodeRabbit Configuration File
🧠 Learnings (4)
AGENTS.md (2)
Learnt from: CR
PR: leynos/mxd#0
File: AGENTS.md:0-0
Timestamp: 2025-06-25T23:37:47.576Z
Learning: For Rust projects: run 'cargo fmt --all', 'cargo clippy -- -D warnings', and 'make test' before committing; fix warnings in code, not by silencing them.
Learnt from: CR
PR: leynos/femtologging#0
File: AGENTS.md:0-0
Timestamp: 2025-06-25T00:03:53.874Z
Learning: For Rust: Run cargo fmt, cargo clippy -- -D warnings, and cargo test before committing; clippy warnings must be disallowed.
docs/rust-testing-with-rstest-fixtures.md (149)
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: In Rust, the rstest crate provides a declarative, macro-based approach to fixture-based and parameterized testing, reducing boilerplate and improving test readability.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: In Rust, the rstest crate enables declarative fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], which inject dependencies as function arguments, improving readability and reducing boilerplate.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], allowing dependencies to be injected as function arguments for improved readability and reduced boilerplate.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros such as #[rstest] and #[fixture], allowing for declarative test setup and dependency injection.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: In Rust, the rstest crate enables declarative fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], which inject dependencies as function arguments and generate multiple test cases from a single function.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], which inject dependencies into test functions by matching argument names to fixture functions.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], allowing dependencies to be injected into test functions as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: Compared to standard Rust #[test], rstest provides declarative fixture injection and parameterization, reducing boilerplate and improving test clarity, especially for complex setups and input combinations.
Learnt from: CR
PR: leynos/lille#0
File: docs/testing-declarative-game-logic-in-dbsp.md:0-0
Timestamp: 2025-07-07T22:05:39.651Z
Learning: Applies to docs/{tests/**/*.{rs},**/*_test.rs} : Use the rstest crate to create reusable, composable test setups (fixtures) for both unit and BDD tests.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that encapsulate setup logic and can return any valid Rust type, including primitives, structs, or trait objects. Fixtures can depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that encapsulate setup logic and can return any valid Rust type, including primitives, structs, or trait objects. Fixtures can depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: rstest is most beneficial for complex setups, parameterized testing, and when aiming for readable, DRY, and maintainable test suites; for simple unit tests, standard #[test] may suffice.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/Cargo.toml : Add `tokio` with `test-util` feature as a development dependency in `Cargo.toml` when using Tokio's test utilities.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that provide setup data or resources for tests. They can return any valid Rust type and can depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Fixtures in rstest are regular Rust functions annotated with #[fixture] and can return any valid Rust type, including primitives, structs, or trait objects. Fixtures can also depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: Fixtures in rstest are regular Rust functions annotated with #[fixture]; their return values are injected into tests by matching argument names, promoting separation of setup and test logic.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: Fixtures in rstest are regular Rust functions annotated with #[fixture]; their return values are injected into test functions by matching argument names, promoting test readability and reusability.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that encapsulate setup logic and can return any valid Rust type, including primitives, structs, or trait objects.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Define fixtures in Rust by annotating functions with `#[fixture]` from the `rstest` crate.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Define fixtures for test setup by annotating Rust functions with `#[fixture]` from the rstest crate.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Define fixtures by annotating Rust functions with `#[fixture]` from the `rstest` crate.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest resolves fixture injection by argument name in the test function signature, following Rust's standard name resolution rules. Careful naming is required to avoid ambiguity when multiple fixtures with the same name are in scope.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: rstest resolves fixture injection by matching argument names in the test function to fixture function names, following Rust's standard name resolution rules. Careful naming is required to avoid ambiguity.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest injects fixtures into test functions by matching argument names to fixture function names, following Rust's standard name resolution rules.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: By default, rstest creates a new instance of a fixture for each test that uses it, ensuring test isolation and preventing shared mutable state between tests.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: By default, rstest creates a new instance of each fixture for every test that uses it, ensuring test isolation and preventing shared mutable state between tests.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: By default, rstest creates a new instance of each fixture for every test that uses it, ensuring test isolation and preventing shared mutable state between tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: By default, rstest creates a new instance of a fixture for each test that uses it, ensuring test isolation and preventing state leakage between tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: By default, rstest creates a new instance of each fixture for every test that uses it, ensuring test isolation and preventing state leakage between tests.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios (each case generates a separate test) and #[values(...)] for combinatorial testing (generating the Cartesian product of values for arguments).
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios (specific input/output pairs) and #[values(...)] for combinatorial testing (Cartesian product of argument values), generating individual test cases for each combination.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: Parameterized tests in rstest are created using #[case(...)] for table-driven scenarios and #[values(...)] for combinatorial testing, generating individual test cases for each set or combination of inputs.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios and #[values(...)] for combinatorial (Cartesian product) testing, generating individual test cases for each combination.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios and #[values(...)] for combinatorial (Cartesian product) testing, generating individual test cases for each combination.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[case(...)] attribute in rstest enables table-driven tests by generating a separate test for each case, with clear reporting for individual failures.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[case(...)] attribute in rstest allows table-driven tests by generating a separate test for each set of input arguments, with each case reported individually by the test runner.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `#[case(...)]` attribute to define table-driven parameterized tests in Rust with `rstest`.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: Fixtures and parameterized arguments (#[case], #[values]) can be combined in the same rstest test function, allowing for expressive and flexible test scenarios.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Fixtures and parameterized arguments (#[case], #[values]) can be combined in the same rstest test function, allowing for expressive and comprehensive test scenarios.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[values(...)] attribute in rstest generates tests for every combination of provided values (Cartesian product), which can lead to a combinatorial explosion in the number of tests if not used judiciously.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[values(...)] attribute in rstest enables combinatorial testing by generating tests for every possible combination of provided values across arguments, which can lead to a combinatorial explosion if not used judiciously.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `#[values(...)]` attribute in `#[rstest]` tests to generate tests for all combinations of provided values (combinatorial testing).
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `#[values(...)]` attribute on test function arguments to generate combinatorial test cases with `rstest`.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use the `#[values(...)]` attribute on test function arguments to generate combinatorial test matrices.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Combine fixtures and parameterized arguments (`#[case]` or `#[values]`) in the same `#[rstest]` test function for expressive test scenarios.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Combine fixtures and parameterized arguments (`#[case]` or `#[values]`) in the same test function for expressive test scenarios.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Combine fixtures and parameterized arguments (`#[case]`, `#[values]`) in the same test function to test variable scenarios within a consistent setup.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Use #[once] fixtures sparingly and only for expensive, read-only, and safely static resources, as their values are never dropped and may cause resource leaks if used for temporary or cleanup-requiring resources.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared across all tests, but the returned value is promoted to 'static' lifetime and is never dropped, making it suitable only for passive or OS-managed resources.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared across all tests, but the returned value is never dropped (static lifetime), making it suitable only for passive or OS-managed resources.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: Use #[once] fixtures only for expensive, read-only, and safely static resources, as they are never dropped and can lead to resource leaks if misused.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.727Z
Learning: Use `#[once]` fixtures only for expensive, read-only, and safely static resources, and prefer regular (per-test) fixtures for test isolation and proper resource cleanup
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: Prefer regular (per-test) fixtures for resources that require cleanup or test isolation; use #[once] only for expensive, read-only, and truly static resources.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared across all tests, but the returned value is never dropped, making it suitable only for static, read-only resources.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Prefer regular (per-test) fixtures for test isolation and proper resource management; use `#[once]` only for expensive, read-only, and safely static resources.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared as a static reference across all tests, but such fixtures are never dropped and cannot be async or generic.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared as a static reference across all tests, but such fixtures are never dropped and cannot be async or generic.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture argument in a test or another fixture, which is useful for destructuring or improving clarity.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Use the `#[from(original_fixture_name)]` attribute to rename a fixture when injecting it as an argument in a test or another fixture.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or improving argument clarity.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is especially useful when destructuring or for clarity.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Use the `#[from(original_fixture_name)]` attribute to rename injected fixture arguments in test or fixture functions
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use the `#[from(original_fixture_name)]` attribute to rename injected fixture arguments in test functions.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.727Z
Learning: Utilize features like `#[from]` for renaming and `#[default]`/`#[with]` for configurable fixtures to enhance clarity and reduce duplication
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: rstest can automatically convert string literals in #[case] or #[values] to types implementing std::str::FromStr, such as std::net::SocketAddr, simplifying test definitions.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest can automatically convert string literals to types implementing std::str::FromStr in #[case] or #[values] attributes, simplifying test definitions for types like SocketAddr.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest can automatically convert string literals in #[case] or #[values] to types implementing std::str::FromStr, simplifying test definitions for types like SocketAddr.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: Asynchronous fixtures and tests are supported by defining async fn fixtures and test functions. rstest integrates with async runtimes like async-std or tokio by combining #[rstest] with the runtime's test attribute.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: rstest supports asynchronous fixtures and tests by allowing async fn for both, and integrates with async runtimes like async-std or tokio by combining #[rstest] with the runtime's #[test] attribute.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest supports async fixtures and async test functions; it integrates with async runtimes like async-std or tokio by using the appropriate test attribute (e.g., #[tokio::test]) alongside #[rstest].
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: rstest supports async fixtures and async test functions; it integrates with async runtimes like async-std or tokio by combining #[rstest] with the appropriate runtime's #[test] attribute.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: rstest supports async fixtures and async test functions; it integrates with async runtimes like async-std or tokio by combining #[rstest] with the runtime's #[test] attribute.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: rstest supports asynchronous testing by allowing async fn fixtures and async test functions, integrating with async runtimes like async-std or tokio via their respective #[async_std::test] or #[tokio::test] attributes.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest supports asynchronous fixtures and tests by allowing async fn for both, and integrates with async runtimes like async-std or tokio by stacking the appropriate test attribute macro.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Define asynchronous fixtures as `async fn` and use them in async test functions with `#[rstest]`.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Write asynchronous tests as `async fn` functions annotated with `#[rstest]` and the appropriate async runtime attribute (e.g., `#[tokio::test]`, `#[async_std::test]`).
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Define asynchronous fixtures as `async fn` and annotate with `#[fixture]` for use in async rstest tests
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Annotate asynchronous test functions with both `#[rstest]` and the appropriate async runtime test attribute (e.g., `#[tokio::test]`, `#[async_std::test]`)
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Annotate asynchronous test functions with both `#[rstest]` and the appropriate async runtime attribute (e.g., `#[tokio::test]`, `#[async_std::test]`).
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The order of procedural macro attributes (e.g., #[rstest] and #[tokio::test]) can matter for correct async test execution; ensure the async runtime's test macro is correctly placed.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing the need for explicit impl Future types and automating .await insertion.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing the need for explicit impl Future types and automating .await calls.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use `#[future]` and `#[awt]` attributes to simplify handling of async fixtures and arguments in tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The order of procedural macro attributes matters when stacking rstest with async runtime macros or conditional test execution macros (e.g., test-with); rstest should typically be applied first to generate the test cases.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, preventing hangs from long-running or stalled operations. A global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, preventing hangs from long-running operations; a global timeout can be set with the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[timeout(...)] attribute in rstest sets a maximum execution time for async tests, preventing hangs from long-running or stalled operations. The RSTEST_TIMEOUT environment variable can set a default timeout for all async tests.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, preventing hangs; a global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, and a global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[timeout(...)] attribute in rstest sets a maximum execution time for async tests, and a global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[timeout(...)] attribute (and RSTEST_TIMEOUT environment variable) can be used to set a maximum execution time for async tests, preventing hangs.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `#[timeout(...)]` attribute to set a maximum execution time for asynchronous tests with `rstest`.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Set timeouts for async rstest tests using the `#[timeout(...)]` attribute or the `RSTEST_TIMEOUT` environment variable
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Apply the `#[timeout(...)]` attribute to async tests to set a maximum execution time and prevent hanging tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Temporary files and directories can be managed in rstest by using fixtures that return types like tempfile::TempDir, leveraging Rust's RAII for automatic cleanup after each test.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: For temporary files and directories, use fixtures that return types like tempfile::TempDir, leveraging Rust's RAII for automatic cleanup after each test.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Temporary files and directories should be managed via fixtures that return objects like tempfile::TempDir, leveraging Rust's RAII for automatic cleanup after each test. Avoid using #[once] for temporary resources to ensure proper cleanup.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Mocking external services (e.g., databases, HTTP APIs) is best encapsulated in fixtures, using crates like mockall or hand-rolled mocks, to keep test logic focused and maintainable.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[files("glob_pattern")] attribute in rstest parameterizes tests over files matching the pattern, injecting either PathBufs or file contents (with mode = "str" or "bytes"). This is powerful for data-driven testing but can increase binary size if embedding large files.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[files("glob_pattern")] attribute in rstest parameterizes tests over files matching a glob, injecting either their PathBuf or contents (as &str or &[u8]) into test arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: The #[files("glob_pattern")] attribute parameterizes tests over files matching a glob, injecting either PathBufs or file contents (with mode = "str" or "bytes") as arguments, enabling data-driven testing from the filesystem.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute on test arguments to inject file paths or contents matching a glob pattern for data-driven tests.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[files("glob_pattern")] attribute in rstest can parameterize tests over files matching a glob, injecting either file paths or file contents as test arguments.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute to inject file paths or contents as test arguments for data-driven tests.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute to inject file paths or contents as test arguments for data-driven tests.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute on test arguments to inject file paths or contents matching the glob pattern
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute to inject file paths or contents as test arguments for data-driven testing.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[files("glob_pattern")] attribute parameterizes tests over files matching a glob, injecting either PathBufs or file contents (as &str or &[u8]) into test arguments, and is useful for data-driven testing.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: Best practices for organizing rstest-based tests include: placing module-local fixtures in the module's tests submodule, sharing fixtures via a common module or crate, using descriptive names, composing small fixtures, and preferring per-test fixtures for isolation.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Best practices for organizing rstest-based tests include grouping related fixtures and tests into modules, using descriptive names, composing small focused fixtures, and preferring per-test fixtures for proper resource management.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Best practices for organizing fixtures and tests include: placing module-specific fixtures in the module's tests submodule, sharing fixtures via a common module or under #[cfg(test)] in the library, using clear naming conventions, composing small focused fixtures, and grouping related tests and fixtures into modules.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: Best practices for organizing fixtures and tests include: placing module-specific fixtures in the module's tests submodule, sharing fixtures via common modules or #[cfg(test)] in the library, using descriptive names, composing small fixtures, and grouping related tests and fixtures into modules.
Learnt from: CR
PR: leynos/wireframe#0
File: AGENTS.md:0-0
Timestamp: 2025-06-30T23:02:18.018Z
Learning: Applies to **/*_test.rs : Use `rstest` fixtures for shared setup.
Learnt from: CR
PR: leynos/netsuke#0
File: AGENTS.md:0-0
Timestamp: 2025-07-18T19:01:42.344Z
Learning: Applies to **/*_test.rs : Use rstest fixtures for shared setup.
Learnt from: CR
PR: leynos/ddlint#0
File: AGENTS.md:0-0
Timestamp: 2025-07-18T18:35:14.627Z
Learning: Applies to **/{tests,src}/**/*_test.rs : Use rstest fixtures for shared setup.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: rstest is most beneficial for complex setups, parameterized testing, and when aiming for readable, DRY, and maintainable test suites; for trivial tests, standard #[test] may suffice.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Use `rstest` for tests with complex setup, parameterization, or where improved readability and reduced boilerplate are desired; for simple unit tests, standard `#[test]` may suffice.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Prefer `rstest` for tests requiring complex setup, parameterization, or improved readability, and use standard `#[test]` for simple unit tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest-generated parameterized tests are named by appending ::case_N to the function name, which aids in identifying and running specific failing cases with cargo test.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest is not suitable for no_std environments, as it depends on the standard library and the test harness.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and test harness.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and test harness.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and test harness.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and the test harness.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and the test harness.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and the test harness.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The rstest-log crate helps integrate logging frameworks into rstest tests, ensuring proper log initialization for each test case.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The rstest-log crate can be used to ensure proper logging initialization in rstest tests, and the test-with crate can be combined with rstest to conditionally execute tests based on runtime conditions.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: For logging in rstest tests, the rstest-log crate can be used to ensure proper initialization of logging frameworks before each test runs.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `logtest` crate to verify log output in tests by capturing and asserting on emitted log records.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `rstest-log` crate to ensure logging frameworks are properly initialized in `rstest`-generated tests.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `rstest-log` crate to ensure logging frameworks are properly initialized in `rstest`-generated tests.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `logtest` crate to assert on log output in tests by starting a `Logger` before running the code under test.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Integrate logging in tests using the `rstest-log` crate to ensure proper log initialization in test cases.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/dependency-analysis.md:0-0
Timestamp: 2025-07-18T18:31:48.692Z
Learning: Applies to docs/{src,tests}/**/*_test.rs : logtest allows asserting on log output in unit tests
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The test-with crate can be combined with rstest to conditionally execute tests based on runtime conditions; macro order matters, with rstest generating test cases before test-with applies its logic.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `test-with` crate to conditionally execute tests based on runtime conditions, annotating after `#[rstest]`.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Conditional test execution (e.g., based on environment variables or file existence) can be achieved by combining rstest with the test-with crate, applying its attributes after rstest's macro expansion.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `test-with` crate to conditionally execute tests based on runtime conditions, applying its attributes after `#[rstest]`.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use the `test-with` crate to conditionally execute tests based on runtime conditions, applying its attributes after `#[rstest]`.
docs/snapshot-testing-in-netsuke-using-insta.md (7)
Learnt from: CR
PR: leynos/netsuke#0
File: docs/snapshot-testing-in-netsuke-using-insta.md:0-0
Timestamp: 2025-07-18T19:05:31.675Z
Learning: Applies to docs/tests/{ir_snapshot_tests.rs,ninja_snapshot_tests.rs,snapshots/ir/**,snapshots/ninja/**} : Organize snapshot tests in the `tests/` directory, with separate modules for IR and Ninja snapshots, and store their snapshots in `tests/snapshots/ir/` and `tests/snapshots/ninja/` respectively
Learnt from: CR
PR: leynos/netsuke#0
File: docs/snapshot-testing-in-netsuke-using-insta.md:0-0
Timestamp: 2025-07-18T19:05:31.675Z
Learning: Applies to docs/tests/ir_snapshot_tests.rs : Write IR snapshot tests in `tests/ir_snapshot_tests.rs` that use deterministic inputs and store snapshots in `tests/snapshots/ir/`
Learnt from: CR
PR: leynos/netsuke#0
File: docs/snapshot-testing-in-netsuke-using-insta.md:0-0
Timestamp: 2025-07-18T19:05:31.675Z
Learning: Applies to docs/tests/ninja_snapshot_tests.rs : Write Ninja snapshot tests in `tests/ninja_snapshot_tests.rs` that use deterministic inputs and store snapshots in `tests/snapshots/ninja/`
Learnt from: CR
PR: leynos/netsuke#0
File: docs/snapshot-testing-in-netsuke-using-insta.md:0-0
Timestamp: 2025-07-18T19:05:31.675Z
Learning: Applies to docs/tests/{ir_snapshot_tests.rs,ninja_snapshot_tests.rs} : Use `Settings::set_snapshot_path` in snapshot tests to direct IR and Ninja snapshots to their respective subdirectories
Learnt from: CR
PR: leynos/netsuke#0
File: docs/roadmap.md:0-0
Timestamp: 2025-07-18T19:04:19.373Z
Learning: Applies to docs/src/ninja_gen.rs : Implement the Ninja file synthesizer in src/ninja_gen.rs to traverse the BuildGraph IR.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/**/ninja_gen.rs : The Ninja file generator must be implemented in 'ninja_gen.rs' and must translate the IR to Ninja syntax, replacing placeholders and ensuring correct quoting.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/snapshot-testing-in-netsuke-using-insta.md:0-0
Timestamp: 2025-07-18T19:05:31.675Z
Learning: Set `INSTA_UPDATE: no` in CI environments to prevent automatic snapshot updates during test runs
docs/netsuke-design.md (5)
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/**/Netsukefile : The 'foreach' entry in 'targets' allows dynamic generation of multiple targets via Jinja evaluation, producing a static build graph after rendering.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/src/ast.rs : The Rust structs representing the Netsukefile schema must be defined in 'src/ast.rs' and annotated with serde attributes for automatic deserialization.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/roadmap.md:0-0
Timestamp: 2025-07-18T19:04:19.373Z
Learning: Applies to docs/src/ast.rs : Implement the YAML parsing logic to deserialize a static Netsukefile into the NetsukeManifest AST.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/src/ast.rs : The 'StringOrList' enum in 'src/ast.rs' must use #[serde(untagged)] to allow fields to accept either a single string or a list of strings.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/**/*.rs : The initial Jinja context for rendering the Netsukefile must be constructed from the 'vars' section of the manifest.
🪛 LanguageTool
docs/rust-testing-with-rstest-fixtures.md
[typographical] ~505-~505: The word ‘When’ starts a question. Add a question mark (“?”) at the end of the sentence.
Context: ...onfigured_item(20, "item_".to_string())`. This hierarchical dependency resolution...
(WRB_QUESTION_MARK)
[style] ~564-~564: Consider a more descriptive alternative.
Context: ...s for Clarity: The #[from] Attribute Sometimes a fixture's function name might be long...
(SOMETIMES_OCCASIONALLY)
[uncategorized] ~592-~592: Use ‘wants’ only when referring to the third person singular such as “he wants”.
Context: ...the test only cares about some parts or wants to use more idiomatic names for destruc...
(CONFUSION_BETWEEN_NNS_OR_WANTS_TO)
[uncategorized] ~1015-~1015: The preposition ‘as’ seems more likely in this position.
Context: ...` attribute. This attribute can be used on a test function argument to inject file...
(AI_HYDRA_LEO_REPLACE_ON_AS)
[duplication] ~1224-~1224: Possible typo: you repeated a word.
Context: ...and running specific failing cases with cargo test test_function_name::case_N. Some IDEs or de...
(ENGLISH_WORD_REPEAT_RULE)
docs/snapshot-testing-in-netsuke-using-insta.md
[uncategorized] ~220-~220: Possible missing comma found.
Context: ...expected IR debug output and Ninja file text respectively. ## Running and Updating ...
(AI_HYDRA_LEO_MISSING_COMMA)
docs/netsuke-design.md
[misspelling] ~24-~24: This word is normally spelled with a hyphen.
Context: ...fulfills this role. It provides a rich, user- friendly language (YAML with Jinja) for describi...
(EN_COMPOUNDS_USER_FRIENDLY)
[uncategorized] ~256-~256: Possible missing comma found.
Context: ...inja's $in and $out macros. After interpolation the command must be parsable by [shle...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~257-~257: Consider using a more formal/concise alternative here.
Context: ...shlex/latest/shlex/). Any interpolation other than ins or outs is automatically shel...
(OTHER_THAN)
[uncategorized] ~316-~316: Loose punctuation mark.
Context: ...ses when kind is omitted. - sources: The input files required by the command...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~655-~655: Loose punctuation mark.
Context: ...quirement: &str) -> Result<bool, Error>`: An example of a domain-specific helpe...
(UNLIKELY_OPENING_PUNCTUATION)
[grammar] ~659-~659: Please add a punctuation mark at the end of paragraph.
Context: ...::Command19, parse the output using the semver` crate 4, and compare it aga...
(PUNCTUATION_PARAGRAPH_END)
[style] ~688-~688: Consider using the typographical ellipsis character here instead.
Context: ...owerful but often opaque functions like $(shell...) and $(wildcard...). Netsuke achieve...
(ELLIPSIS)
[style] ~689-~689: Consider using the typographical ellipsis character here instead.
Context: ...opaque functions like $(shell...) and $(wildcard...). Netsuke achieves and surpasses this ...
(ELLIPSIS)
[style] ~704-~704: The serial comma (Oxford comma, Harvard comma) is missing.
Context: ...library" of Jinja helpers. These tests, filters and functions are available to every templa...
(SERIAL_COMMA_ON)
[misspelling] ~1064-~1064: This word is normally spelled with a hyphen.
Context: ...ect shell quoting falls on the user, an error- prone task that requires specialized knowledg...
(EN_COMPOUNDS_ERROR_PRONE)
[style] ~1270-~1270: Would you like to use the Oxford spelling “Visualizing”? The spelling ‘Visualising’ is also correct.
Context: ...l` using an embedded Dagre.js viewer. Visualising the graph is invaluable for understandi...
(OXFORD_SPELLING_Z_NOT_S)
[grammar] ~1275-~1275: An apostrophe ‘s’ denotes possession. Did you mean to use the plural form of the noun (no apostrophe)?
Context: ...Decisions The CLI is implemented using clap's derive API in src/cli.rs. Clap's `def...
(NOUN_APOSTROPHE_S_VERB)
[style] ~1314-~1314: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ile generator (ninja_gen.rs). 1. Implement the std::process::Command logic to in...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~1336-~1336: Consider using the typographical ellipsis character here instead.
Context: ... 1. Implement basic Jinja control flow ({% if... %}, {% for... %}) and variabl...
(ELLIPSIS)
[style] ~1336-~1336: Consider using the typographical ellipsis character here instead.
Context: ...asic Jinja control flow ({% if... %}, {% for... %}) and variable substitution. ...
(ELLIPSIS)
🔇 Additional comments (2)
docs/roadmap.md (1)
3-5: No issues spotted in the re-flowed introThe wrapping change keeps meaning intact and respects the 80-column rule.
AGENTS.md (1)
12-13: Line-wrap looks correctThe bullet now wraps at ≤80 columns and preserves list indentation.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 6
🔭 Outside diff range comments (3)
docs/rust-testing-with-rstest-fixtures.md (3)
405-406: Fix invalid Rust syntax in code exampleThe leading
#inside the parameter list breaks compilation and is not the
standard doc-test hiding pattern. Drop it.- # initial_state: State, + initial_state: State,
620-623: Remove stray#in fixture parameter listThe
#renders the snippet uncompilable. It should not appear within a
function signature.- # name: &str, + name: &str,
646-648: Eliminate#token in test functionThe parameter marker breaks the example and distracts readers.
-fn test_custom_name_user(# user_fixture: User) { +fn test_custom_name_user(user_fixture: User) {
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (3)
docs/netsuke-design.md(39 hunks)docs/rust-testing-with-rstest-fixtures.md(33 hunks)docs/snapshot-testing-in-netsuke-using-insta.md(14 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
docs/**/*.md
Instructions used from:
Sources:
📄 CodeRabbit Inference Engine
- AGENTS.md
**/*.md
Instructions used from:
Sources:
📄 CodeRabbit Inference Engine
- AGENTS.md
⚙️ CodeRabbit Configuration File
🧠 Learnings (3)
docs/snapshot-testing-in-netsuke-using-insta.md (7)
Learnt from: CR
PR: leynos/netsuke#0
File: docs/snapshot-testing-in-netsuke-using-insta.md:0-0
Timestamp: 2025-07-18T19:05:31.675Z
Learning: Applies to docs/tests/{ir_snapshot_tests.rs,ninja_snapshot_tests.rs,snapshots/ir/**,snapshots/ninja/**} : Organize snapshot tests in the `tests/` directory, with separate modules for IR and Ninja snapshots, and store their snapshots in `tests/snapshots/ir/` and `tests/snapshots/ninja/` respectively
Learnt from: CR
PR: leynos/netsuke#0
File: docs/snapshot-testing-in-netsuke-using-insta.md:0-0
Timestamp: 2025-07-18T19:05:31.675Z
Learning: Applies to docs/tests/ir_snapshot_tests.rs : Write IR snapshot tests in `tests/ir_snapshot_tests.rs` that use deterministic inputs and store snapshots in `tests/snapshots/ir/`
Learnt from: CR
PR: leynos/netsuke#0
File: docs/snapshot-testing-in-netsuke-using-insta.md:0-0
Timestamp: 2025-07-18T19:05:31.675Z
Learning: Applies to docs/tests/ninja_snapshot_tests.rs : Write Ninja snapshot tests in `tests/ninja_snapshot_tests.rs` that use deterministic inputs and store snapshots in `tests/snapshots/ninja/`
Learnt from: CR
PR: leynos/netsuke#0
File: docs/snapshot-testing-in-netsuke-using-insta.md:0-0
Timestamp: 2025-07-18T19:05:31.675Z
Learning: Applies to docs/tests/{ir_snapshot_tests.rs,ninja_snapshot_tests.rs} : Use `Settings::set_snapshot_path` in snapshot tests to direct IR and Ninja snapshots to their respective subdirectories
Learnt from: CR
PR: leynos/netsuke#0
File: docs/roadmap.md:0-0
Timestamp: 2025-07-18T19:04:19.373Z
Learning: Applies to docs/src/ninja_gen.rs : Implement the Ninja file synthesizer in src/ninja_gen.rs to traverse the BuildGraph IR.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/**/ninja_gen.rs : The Ninja file generator must be implemented in 'ninja_gen.rs' and must translate the IR to Ninja syntax, replacing placeholders and ensuring correct quoting.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/snapshot-testing-in-netsuke-using-insta.md:0-0
Timestamp: 2025-07-18T19:05:31.675Z
Learning: Set `INSTA_UPDATE: no` in CI environments to prevent automatic snapshot updates during test runs
docs/netsuke-design.md (5)
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/**/Netsukefile : The 'foreach' entry in 'targets' allows dynamic generation of multiple targets via Jinja evaluation, producing a static build graph after rendering.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/src/ast.rs : The Rust structs representing the Netsukefile schema must be defined in 'src/ast.rs' and annotated with serde attributes for automatic deserialization.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/roadmap.md:0-0
Timestamp: 2025-07-18T19:04:19.373Z
Learning: Applies to docs/src/ast.rs : Implement the YAML parsing logic to deserialize a static Netsukefile into the NetsukeManifest AST.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/src/ast.rs : The 'StringOrList' enum in 'src/ast.rs' must use #[serde(untagged)] to allow fields to accept either a single string or a list of strings.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/**/*.rs : The initial Jinja context for rendering the Netsukefile must be constructed from the 'vars' section of the manifest.
docs/rust-testing-with-rstest-fixtures.md (148)
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: In Rust, the rstest crate provides a declarative, macro-based approach to fixture-based and parameterized testing, reducing boilerplate and improving test readability.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: In Rust, the rstest crate enables declarative fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], which inject dependencies as function arguments, improving readability and reducing boilerplate.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], allowing dependencies to be injected as function arguments for improved readability and reduced boilerplate.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros such as #[rstest] and #[fixture], allowing for declarative test setup and dependency injection.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: In Rust, the rstest crate enables declarative fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], which inject dependencies as function arguments and generate multiple test cases from a single function.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], which inject dependencies into test functions by matching argument names to fixture functions.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], allowing dependencies to be injected into test functions as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: Compared to standard Rust #[test], rstest provides declarative fixture injection and parameterization, reducing boilerplate and improving test clarity, especially for complex setups and input combinations.
Learnt from: CR
PR: leynos/lille#0
File: docs/testing-declarative-game-logic-in-dbsp.md:0-0
Timestamp: 2025-07-07T22:05:39.651Z
Learning: Applies to docs/{tests/**/*.{rs},**/*_test.rs} : Use the rstest crate to create reusable, composable test setups (fixtures) for both unit and BDD tests.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that encapsulate setup logic and can return any valid Rust type, including primitives, structs, or trait objects. Fixtures can depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that encapsulate setup logic and can return any valid Rust type, including primitives, structs, or trait objects. Fixtures can depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: rstest is most beneficial for complex setups, parameterized testing, and when aiming for readable, DRY, and maintainable test suites; for simple unit tests, standard #[test] may suffice.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/Cargo.toml : Add `tokio` with `test-util` feature as a development dependency in `Cargo.toml` when using Tokio's test utilities.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that provide setup data or resources for tests. They can return any valid Rust type and can depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Fixtures in rstest are regular Rust functions annotated with #[fixture] and can return any valid Rust type, including primitives, structs, or trait objects. Fixtures can also depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: Fixtures in rstest are regular Rust functions annotated with #[fixture]; their return values are injected into tests by matching argument names, promoting separation of setup and test logic.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: Fixtures in rstest are regular Rust functions annotated with #[fixture]; their return values are injected into test functions by matching argument names, promoting test readability and reusability.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that encapsulate setup logic and can return any valid Rust type, including primitives, structs, or trait objects.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Define fixtures in Rust by annotating functions with `#[fixture]` from the `rstest` crate.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Define fixtures for test setup by annotating Rust functions with `#[fixture]` from the rstest crate.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Define fixtures by annotating Rust functions with `#[fixture]` from the `rstest` crate.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest resolves fixture injection by argument name in the test function signature, following Rust's standard name resolution rules. Careful naming is required to avoid ambiguity when multiple fixtures with the same name are in scope.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: rstest resolves fixture injection by matching argument names in the test function to fixture function names, following Rust's standard name resolution rules. Careful naming is required to avoid ambiguity.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest injects fixtures into test functions by matching argument names to fixture function names, following Rust's standard name resolution rules.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: By default, rstest creates a new instance of a fixture for each test that uses it, ensuring test isolation and preventing shared mutable state between tests.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: By default, rstest creates a new instance of each fixture for every test that uses it, ensuring test isolation and preventing shared mutable state between tests.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: By default, rstest creates a new instance of each fixture for every test that uses it, ensuring test isolation and preventing shared mutable state between tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: By default, rstest creates a new instance of a fixture for each test that uses it, ensuring test isolation and preventing state leakage between tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: By default, rstest creates a new instance of each fixture for every test that uses it, ensuring test isolation and preventing state leakage between tests.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios (each case generates a separate test) and #[values(...)] for combinatorial testing (generating the Cartesian product of values for arguments).
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios (specific input/output pairs) and #[values(...)] for combinatorial testing (Cartesian product of argument values), generating individual test cases for each combination.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: Parameterized tests in rstest are created using #[case(...)] for table-driven scenarios and #[values(...)] for combinatorial testing, generating individual test cases for each set or combination of inputs.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios and #[values(...)] for combinatorial (Cartesian product) testing, generating individual test cases for each combination.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios and #[values(...)] for combinatorial (Cartesian product) testing, generating individual test cases for each combination.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[case(...)] attribute in rstest enables table-driven tests by generating a separate test for each case, with clear reporting for individual failures.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[case(...)] attribute in rstest allows table-driven tests by generating a separate test for each set of input arguments, with each case reported individually by the test runner.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `#[case(...)]` attribute to define table-driven parameterized tests in Rust with `rstest`.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: Fixtures and parameterized arguments (#[case], #[values]) can be combined in the same rstest test function, allowing for expressive and flexible test scenarios.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Fixtures and parameterized arguments (#[case], #[values]) can be combined in the same rstest test function, allowing for expressive and comprehensive test scenarios.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[values(...)] attribute in rstest generates tests for every combination of provided values (Cartesian product), which can lead to a combinatorial explosion in the number of tests if not used judiciously.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[values(...)] attribute in rstest enables combinatorial testing by generating tests for every possible combination of provided values across arguments, which can lead to a combinatorial explosion if not used judiciously.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `#[values(...)]` attribute in `#[rstest]` tests to generate tests for all combinations of provided values (combinatorial testing).
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `#[values(...)]` attribute on test function arguments to generate combinatorial test cases with `rstest`.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use the `#[values(...)]` attribute on test function arguments to generate combinatorial test matrices.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Combine fixtures and parameterized arguments (`#[case]` or `#[values]`) in the same `#[rstest]` test function for expressive test scenarios.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Combine fixtures and parameterized arguments (`#[case]` or `#[values]`) in the same test function for expressive test scenarios.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Combine fixtures and parameterized arguments (`#[case]`, `#[values]`) in the same test function to test variable scenarios within a consistent setup.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Use #[once] fixtures sparingly and only for expensive, read-only, and safely static resources, as their values are never dropped and may cause resource leaks if used for temporary or cleanup-requiring resources.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared across all tests, but the returned value is promoted to 'static' lifetime and is never dropped, making it suitable only for passive or OS-managed resources.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared across all tests, but the returned value is never dropped (static lifetime), making it suitable only for passive or OS-managed resources.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: Use #[once] fixtures only for expensive, read-only, and safely static resources, as they are never dropped and can lead to resource leaks if misused.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.727Z
Learning: Use `#[once]` fixtures only for expensive, read-only, and safely static resources, and prefer regular (per-test) fixtures for test isolation and proper resource cleanup
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: Prefer regular (per-test) fixtures for resources that require cleanup or test isolation; use #[once] only for expensive, read-only, and truly static resources.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared across all tests, but the returned value is never dropped, making it suitable only for static, read-only resources.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Prefer regular (per-test) fixtures for test isolation and proper resource management; use `#[once]` only for expensive, read-only, and safely static resources.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared as a static reference across all tests, but such fixtures are never dropped and cannot be async or generic.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared as a static reference across all tests, but such fixtures are never dropped and cannot be async or generic.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture argument in a test or another fixture, which is useful for destructuring or improving clarity.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Use the `#[from(original_fixture_name)]` attribute to rename a fixture when injecting it as an argument in a test or another fixture.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or improving argument clarity.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is especially useful when destructuring or for clarity.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Use the `#[from(original_fixture_name)]` attribute to rename injected fixture arguments in test or fixture functions
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use the `#[from(original_fixture_name)]` attribute to rename injected fixture arguments in test functions.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.727Z
Learning: Utilize features like `#[from]` for renaming and `#[default]`/`#[with]` for configurable fixtures to enhance clarity and reduce duplication
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: rstest can automatically convert string literals in #[case] or #[values] to types implementing std::str::FromStr, such as std::net::SocketAddr, simplifying test definitions.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest can automatically convert string literals to types implementing std::str::FromStr in #[case] or #[values] attributes, simplifying test definitions for types like SocketAddr.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest can automatically convert string literals in #[case] or #[values] to types implementing std::str::FromStr, simplifying test definitions for types like SocketAddr.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: Asynchronous fixtures and tests are supported by defining async fn fixtures and test functions. rstest integrates with async runtimes like async-std or tokio by combining #[rstest] with the runtime's test attribute.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: rstest supports asynchronous fixtures and tests by allowing async fn for both, and integrates with async runtimes like async-std or tokio by combining #[rstest] with the runtime's #[test] attribute.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest supports async fixtures and async test functions; it integrates with async runtimes like async-std or tokio by using the appropriate test attribute (e.g., #[tokio::test]) alongside #[rstest].
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: rstest supports async fixtures and async test functions; it integrates with async runtimes like async-std or tokio by combining #[rstest] with the appropriate runtime's #[test] attribute.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: rstest supports async fixtures and async test functions; it integrates with async runtimes like async-std or tokio by combining #[rstest] with the runtime's #[test] attribute.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: rstest supports asynchronous testing by allowing async fn fixtures and async test functions, integrating with async runtimes like async-std or tokio via their respective #[async_std::test] or #[tokio::test] attributes.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest supports asynchronous fixtures and tests by allowing async fn for both, and integrates with async runtimes like async-std or tokio by stacking the appropriate test attribute macro.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Define asynchronous fixtures as `async fn` and use them in async test functions with `#[rstest]`.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Write asynchronous tests as `async fn` functions annotated with `#[rstest]` and the appropriate async runtime attribute (e.g., `#[tokio::test]`, `#[async_std::test]`).
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Define asynchronous fixtures as `async fn` and annotate with `#[fixture]` for use in async rstest tests
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Annotate asynchronous test functions with both `#[rstest]` and the appropriate async runtime test attribute (e.g., `#[tokio::test]`, `#[async_std::test]`)
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Annotate asynchronous test functions with both `#[rstest]` and the appropriate async runtime attribute (e.g., `#[tokio::test]`, `#[async_std::test]`).
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The order of procedural macro attributes (e.g., #[rstest] and #[tokio::test]) can matter for correct async test execution; ensure the async runtime's test macro is correctly placed.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing the need for explicit impl Future types and automating .await insertion.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing the need for explicit impl Future types and automating .await calls.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use `#[future]` and `#[awt]` attributes to simplify handling of async fixtures and arguments in tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, preventing hangs from long-running or stalled operations. A global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, preventing hangs from long-running operations; a global timeout can be set with the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[timeout(...)] attribute in rstest sets a maximum execution time for async tests, preventing hangs from long-running or stalled operations. The RSTEST_TIMEOUT environment variable can set a default timeout for all async tests.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, preventing hangs; a global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, and a global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[timeout(...)] attribute in rstest sets a maximum execution time for async tests, and a global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[timeout(...)] attribute (and RSTEST_TIMEOUT environment variable) can be used to set a maximum execution time for async tests, preventing hangs.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `#[timeout(...)]` attribute to set a maximum execution time for asynchronous tests with `rstest`.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Set timeouts for async rstest tests using the `#[timeout(...)]` attribute or the `RSTEST_TIMEOUT` environment variable
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Apply the `#[timeout(...)]` attribute to async tests to set a maximum execution time and prevent hanging tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Temporary files and directories can be managed in rstest by using fixtures that return types like tempfile::TempDir, leveraging Rust's RAII for automatic cleanup after each test.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: For temporary files and directories, use fixtures that return types like tempfile::TempDir, leveraging Rust's RAII for automatic cleanup after each test.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Temporary files and directories should be managed via fixtures that return objects like tempfile::TempDir, leveraging Rust's RAII for automatic cleanup after each test. Avoid using #[once] for temporary resources to ensure proper cleanup.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Mocking external services (e.g., databases, HTTP APIs) is best encapsulated in fixtures, using crates like mockall or hand-rolled mocks, to keep test logic focused and maintainable.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[files("glob_pattern")] attribute in rstest parameterizes tests over files matching the pattern, injecting either PathBufs or file contents (with mode = "str" or "bytes"). This is powerful for data-driven testing but can increase binary size if embedding large files.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[files("glob_pattern")] attribute in rstest parameterizes tests over files matching a glob, injecting either their PathBuf or contents (as &str or &[u8]) into test arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: The #[files("glob_pattern")] attribute parameterizes tests over files matching a glob, injecting either PathBufs or file contents (with mode = "str" or "bytes") as arguments, enabling data-driven testing from the filesystem.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute on test arguments to inject file paths or contents matching a glob pattern for data-driven tests.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[files("glob_pattern")] attribute in rstest can parameterize tests over files matching a glob, injecting either file paths or file contents as test arguments.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute to inject file paths or contents as test arguments for data-driven tests.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute to inject file paths or contents as test arguments for data-driven tests.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute to inject file paths or contents as test arguments for data-driven testing.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute on test arguments to inject file paths or contents matching the glob pattern
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[files("glob_pattern")] attribute parameterizes tests over files matching a glob, injecting either PathBufs or file contents (as &str or &[u8]) into test arguments, and is useful for data-driven testing.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: Best practices for organizing rstest-based tests include: placing module-local fixtures in the module's tests submodule, sharing fixtures via a common module or crate, using descriptive names, composing small fixtures, and preferring per-test fixtures for isolation.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Best practices for organizing rstest-based tests include grouping related fixtures and tests into modules, using descriptive names, composing small focused fixtures, and preferring per-test fixtures for proper resource management.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Best practices for organizing fixtures and tests include: placing module-specific fixtures in the module's tests submodule, sharing fixtures via a common module or under #[cfg(test)] in the library, using clear naming conventions, composing small focused fixtures, and grouping related tests and fixtures into modules.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: Best practices for organizing fixtures and tests include: placing module-specific fixtures in the module's tests submodule, sharing fixtures via common modules or #[cfg(test)] in the library, using descriptive names, composing small fixtures, and grouping related tests and fixtures into modules.
Learnt from: CR
PR: leynos/wireframe#0
File: AGENTS.md:0-0
Timestamp: 2025-06-30T23:02:18.018Z
Learning: Applies to **/*_test.rs : Use `rstest` fixtures for shared setup.
Learnt from: CR
PR: leynos/netsuke#0
File: AGENTS.md:0-0
Timestamp: 2025-07-18T19:01:42.344Z
Learning: Applies to **/*_test.rs : Use rstest fixtures for shared setup.
Learnt from: CR
PR: leynos/ddlint#0
File: AGENTS.md:0-0
Timestamp: 2025-07-18T18:35:14.627Z
Learning: Applies to **/{tests,src}/**/*_test.rs : Use rstest fixtures for shared setup.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: rstest is most beneficial for complex setups, parameterized testing, and when aiming for readable, DRY, and maintainable test suites; for trivial tests, standard #[test] may suffice.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Use `rstest` for tests with complex setup, parameterization, or where improved readability and reduced boilerplate are desired; for simple unit tests, standard `#[test]` may suffice.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Prefer `rstest` for tests requiring complex setup, parameterization, or improved readability, and use standard `#[test]` for simple unit tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest-generated parameterized tests are named by appending ::case_N to the function name, which aids in identifying and running specific failing cases with cargo test.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest is not suitable for no_std environments, as it depends on the standard library and the test harness.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and test harness.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and test harness.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and test harness.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and the test harness.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and the test harness.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and the test harness.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The rstest-log crate helps integrate logging frameworks into rstest tests, ensuring proper log initialization for each test case.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The rstest-log crate can be used to ensure proper logging initialization in rstest tests, and the test-with crate can be combined with rstest to conditionally execute tests based on runtime conditions.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: For logging in rstest tests, the rstest-log crate can be used to ensure proper initialization of logging frameworks before each test runs.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `logtest` crate to verify log output in tests by capturing and asserting on emitted log records.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `rstest-log` crate to ensure logging frameworks are properly initialized in `rstest`-generated tests.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `rstest-log` crate to ensure logging frameworks are properly initialized in `rstest`-generated tests.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `logtest` crate to assert on log output in tests by starting a `Logger` before running the code under test.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Integrate logging in tests using the `rstest-log` crate to ensure proper log initialization in test cases.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/dependency-analysis.md:0-0
Timestamp: 2025-07-18T18:31:48.692Z
Learning: Applies to docs/{src,tests}/**/*_test.rs : logtest allows asserting on log output in unit tests
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The test-with crate can be combined with rstest to conditionally execute tests based on runtime conditions; macro order matters, with rstest generating test cases before test-with applies its logic.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `test-with` crate to conditionally execute tests based on runtime conditions, annotating after `#[rstest]`.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Conditional test execution (e.g., based on environment variables or file existence) can be achieved by combining rstest with the test-with crate, applying its attributes after rstest's macro expansion.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `test-with` crate to conditionally execute tests based on runtime conditions, applying its attributes after `#[rstest]`.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use the `test-with` crate to conditionally execute tests based on runtime conditions, applying its attributes after `#[rstest]`.
🪛 LanguageTool
docs/snapshot-testing-in-netsuke-using-insta.md
[uncategorized] ~220-~220: Possible missing comma found.
Context: ...expected IR debug output and Ninja file text respectively. ## Running and Updating ...
(AI_HYDRA_LEO_MISSING_COMMA)
docs/netsuke-design.md
[uncategorized] ~257-~257: Possible missing comma found.
Context: ...inja's $in and $out macros. After interpolation the command must be parsable by [shle...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~258-~258: Consider using a more formal/concise alternative here.
Context: ...shlex/latest/shlex/). Any interpolation other than ins or outs is automatically shel...
(OTHER_THAN)
[uncategorized] ~317-~317: Loose punctuation mark.
Context: ...ses when kind is omitted. - sources: The input files required by the command...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~656-~656: Loose punctuation mark.
Context: ...quirement: &str) -> Result<bool, Error>`: An example of a domain-specific helpe...
(UNLIKELY_OPENING_PUNCTUATION)
[grammar] ~660-~660: Please add a punctuation mark at the end of paragraph.
Context: ...::Command19, parse the output using the semver` crate 4, and compare it aga...
(PUNCTUATION_PARAGRAPH_END)
[style] ~689-~689: Consider using the typographical ellipsis character here instead.
Context: ...owerful but often opaque functions like $(shell...) and $(wildcard...). Netsuke achieve...
(ELLIPSIS)
[style] ~690-~690: Consider using the typographical ellipsis character here instead.
Context: ...opaque functions like $(shell...) and $(wildcard...). Netsuke achieves and surpasses this ...
(ELLIPSIS)
[style] ~705-~705: The serial comma (Oxford comma, Harvard comma) is missing.
Context: ...library" of Jinja helpers. These tests, filters and functions are available to every templa...
(SERIAL_COMMA_ON)
[style] ~1271-~1271: Would you like to use the Oxford spelling “Visualizing”? The spelling ‘Visualising’ is also correct.
Context: ...l` using an embedded Dagre.js viewer. Visualising the graph is invaluable for understandi...
(OXFORD_SPELLING_Z_NOT_S)
[grammar] ~1276-~1276: An apostrophe ‘s’ denotes possession. Did you mean to use the plural form of the noun (no apostrophe)?
Context: ...Decisions The CLI is implemented using clap's derive API in src/cli.rs. Clap's `def...
(NOUN_APOSTROPHE_S_VERB)
[style] ~1315-~1315: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ile generator (ninja_gen.rs). 1. Implement the std::process::Command logic to in...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~1337-~1337: Consider using the typographical ellipsis character here instead.
Context: ... 1. Implement basic Jinja control flow ({% if... %}, {% for... %}) and variabl...
(ELLIPSIS)
[style] ~1337-~1337: Consider using the typographical ellipsis character here instead.
Context: ...asic Jinja control flow ({% if... %}, {% for... %}) and variable substitution. ...
(ELLIPSIS)
docs/rust-testing-with-rstest-fixtures.md
[typographical] ~505-~505: The word ‘When’ starts a question. Add a question mark (“?”) at the end of the sentence.
Context: ...onfigured_item(20, "item_".to_string())`. This hierarchical dependency resolution...
(WRB_QUESTION_MARK)
[style] ~564-~564: Consider a more descriptive alternative.
Context: ...s for Clarity: The #[from] Attribute Sometimes a fixture's function name might be long...
(SOMETIMES_OCCASIONALLY)
[uncategorized] ~592-~592: Use ‘wants’ only when referring to the third person singular such as “he wants”.
Context: ...the test only cares about some parts or wants to use more idiomatic names for destruc...
(CONFUSION_BETWEEN_NNS_OR_WANTS_TO)
[uncategorized] ~1015-~1015: The preposition ‘as’ seems more likely in this position.
Context: ...` attribute. This attribute can be used on a test function argument to inject file...
(AI_HYDRA_LEO_REPLACE_ON_AS)
[duplication] ~1224-~1224: Possible typo: you repeated a word.
Context: ...and running specific failing cases with cargo test test_function_name::case_N. Some IDEs or de...
(ENGLISH_WORD_REPEAT_RULE)
Comment on lines
+218
to
+220
| `tests/snapshots/ninja/simple_manifest_ninja.snap` (or combined snapshot files | ||
| per test module). These snapshot files contain the expected IR debug output and | ||
| Ninja file text respectively. |
Contributor
There was a problem hiding this comment.
Insert blank line before heading
A heading must be preceded by an empty line; otherwise markdown renders it as
plain text.
-Ninja file text respectively. ## Running and Updating Snapshot Tests
-
+Ninja file text respectively.
+
+## Running and Updating Snapshot Tests📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| `tests/snapshots/ninja/simple_manifest_ninja.snap` (or combined snapshot files | |
| per test module). These snapshot files contain the expected IR debug output and | |
| Ninja file text respectively. | |
| `tests/snapshots/ninja/simple_manifest_ninja.snap` (or combined snapshot files | |
| per test module). These snapshot files contain the expected IR debug output and | |
| Ninja file text respectively. | |
| ## Running and Updating Snapshot Tests |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~220-~220: Possible missing comma found.
Context: ...expected IR debug output and Ninja file text respectively. ## Running and Updating ...
(AI_HYDRA_LEO_MISSING_COMMA)
🤖 Prompt for AI Agents
In docs/snapshot-testing-in-netsuke-using-insta.md around lines 218 to 220,
insert a blank line before the heading to ensure it is rendered correctly as a
heading in markdown instead of plain text.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🔭 Outside diff range comments (1)
docs/rust-testing-with-rstest-fixtures.md (1)
107-108: Replace second-person pronoun in installation noteAvoid “your” to comply with the docs style guide.
-Add the following lines to your `Cargo.toml` under the `[dev-dependencies]` section: +Add the following lines to the project’s `Cargo.toml` under the `[dev-dependencies]` section:
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (3)
docs/behavioural-testing-in-rust-with-cucumber.md(1 hunks)docs/netsuke-design.md(40 hunks)docs/rust-testing-with-rstest-fixtures.md(36 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
docs/**/*.md
Instructions used from:
Sources:
📄 CodeRabbit Inference Engine
- AGENTS.md
**/*.md
Instructions used from:
Sources:
📄 CodeRabbit Inference Engine
- AGENTS.md
⚙️ CodeRabbit Configuration File
🧠 Learnings (2)
docs/rust-testing-with-rstest-fixtures.md (148)
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: In Rust, the rstest crate provides a declarative, macro-based approach to fixture-based and parameterized testing, reducing boilerplate and improving test readability.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: In Rust, the rstest crate enables declarative fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], which inject dependencies as function arguments, improving readability and reducing boilerplate.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], allowing dependencies to be injected as function arguments for improved readability and reduced boilerplate.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros such as #[rstest] and #[fixture], allowing for declarative test setup and dependency injection.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: In Rust, the rstest crate enables declarative fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], which inject dependencies as function arguments and generate multiple test cases from a single function.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], which inject dependencies into test functions by matching argument names to fixture functions.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], allowing dependencies to be injected into test functions as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: Compared to standard Rust #[test], rstest provides declarative fixture injection and parameterization, reducing boilerplate and improving test clarity, especially for complex setups and input combinations.
Learnt from: CR
PR: leynos/lille#0
File: docs/testing-declarative-game-logic-in-dbsp.md:0-0
Timestamp: 2025-07-07T22:05:39.651Z
Learning: Applies to docs/{tests/**/*.{rs},**/*_test.rs} : Use the rstest crate to create reusable, composable test setups (fixtures) for both unit and BDD tests.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that encapsulate setup logic and can return any valid Rust type, including primitives, structs, or trait objects. Fixtures can depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that encapsulate setup logic and can return any valid Rust type, including primitives, structs, or trait objects. Fixtures can depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: rstest is most beneficial for complex setups, parameterized testing, and when aiming for readable, DRY, and maintainable test suites; for simple unit tests, standard #[test] may suffice.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/Cargo.toml : Add `tokio` with `test-util` feature as a development dependency in `Cargo.toml` when using Tokio's test utilities.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that provide setup data or resources for tests. They can return any valid Rust type and can depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Fixtures in rstest are regular Rust functions annotated with #[fixture] and can return any valid Rust type, including primitives, structs, or trait objects. Fixtures can also depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: Fixtures in rstest are regular Rust functions annotated with #[fixture]; their return values are injected into tests by matching argument names, promoting separation of setup and test logic.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: Fixtures in rstest are regular Rust functions annotated with #[fixture]; their return values are injected into test functions by matching argument names, promoting test readability and reusability.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that encapsulate setup logic and can return any valid Rust type, including primitives, structs, or trait objects.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Define fixtures in Rust by annotating functions with `#[fixture]` from the `rstest` crate.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Define fixtures for test setup by annotating Rust functions with `#[fixture]` from the rstest crate.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Define fixtures by annotating Rust functions with `#[fixture]` from the `rstest` crate.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest resolves fixture injection by argument name in the test function signature, following Rust's standard name resolution rules. Careful naming is required to avoid ambiguity when multiple fixtures with the same name are in scope.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: rstest resolves fixture injection by matching argument names in the test function to fixture function names, following Rust's standard name resolution rules. Careful naming is required to avoid ambiguity.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest injects fixtures into test functions by matching argument names to fixture function names, following Rust's standard name resolution rules.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: By default, rstest creates a new instance of a fixture for each test that uses it, ensuring test isolation and preventing shared mutable state between tests.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: By default, rstest creates a new instance of each fixture for every test that uses it, ensuring test isolation and preventing shared mutable state between tests.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: By default, rstest creates a new instance of each fixture for every test that uses it, ensuring test isolation and preventing shared mutable state between tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: By default, rstest creates a new instance of a fixture for each test that uses it, ensuring test isolation and preventing state leakage between tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: By default, rstest creates a new instance of each fixture for every test that uses it, ensuring test isolation and preventing state leakage between tests.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios (each case generates a separate test) and #[values(...)] for combinatorial testing (generating the Cartesian product of values for arguments).
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios (specific input/output pairs) and #[values(...)] for combinatorial testing (Cartesian product of argument values), generating individual test cases for each combination.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: Parameterized tests in rstest are created using #[case(...)] for table-driven scenarios and #[values(...)] for combinatorial testing, generating individual test cases for each set or combination of inputs.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios and #[values(...)] for combinatorial (Cartesian product) testing, generating individual test cases for each combination.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios and #[values(...)] for combinatorial (Cartesian product) testing, generating individual test cases for each combination.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[case(...)] attribute in rstest enables table-driven tests by generating a separate test for each case, with clear reporting for individual failures.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[case(...)] attribute in rstest allows table-driven tests by generating a separate test for each set of input arguments, with each case reported individually by the test runner.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `#[case(...)]` attribute to define table-driven parameterized tests in Rust with `rstest`.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: Fixtures and parameterized arguments (#[case], #[values]) can be combined in the same rstest test function, allowing for expressive and flexible test scenarios.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Fixtures and parameterized arguments (#[case], #[values]) can be combined in the same rstest test function, allowing for expressive and comprehensive test scenarios.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[values(...)] attribute in rstest generates tests for every combination of provided values (Cartesian product), which can lead to a combinatorial explosion in the number of tests if not used judiciously.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[values(...)] attribute in rstest enables combinatorial testing by generating tests for every possible combination of provided values across arguments, which can lead to a combinatorial explosion if not used judiciously.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `#[values(...)]` attribute in `#[rstest]` tests to generate tests for all combinations of provided values (combinatorial testing).
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `#[values(...)]` attribute on test function arguments to generate combinatorial test cases with `rstest`.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use the `#[values(...)]` attribute on test function arguments to generate combinatorial test matrices.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Combine fixtures and parameterized arguments (`#[case]` or `#[values]`) in the same `#[rstest]` test function for expressive test scenarios.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Combine fixtures and parameterized arguments (`#[case]` or `#[values]`) in the same test function for expressive test scenarios.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Combine fixtures and parameterized arguments (`#[case]`, `#[values]`) in the same test function to test variable scenarios within a consistent setup.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Use #[once] fixtures sparingly and only for expensive, read-only, and safely static resources, as their values are never dropped and may cause resource leaks if used for temporary or cleanup-requiring resources.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared across all tests, but the returned value is promoted to 'static' lifetime and is never dropped, making it suitable only for passive or OS-managed resources.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared across all tests, but the returned value is never dropped (static lifetime), making it suitable only for passive or OS-managed resources.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: Use #[once] fixtures only for expensive, read-only, and safely static resources, as they are never dropped and can lead to resource leaks if misused.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.727Z
Learning: Use `#[once]` fixtures only for expensive, read-only, and safely static resources, and prefer regular (per-test) fixtures for test isolation and proper resource cleanup
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: Prefer regular (per-test) fixtures for resources that require cleanup or test isolation; use #[once] only for expensive, read-only, and truly static resources.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared across all tests, but the returned value is never dropped, making it suitable only for static, read-only resources.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Prefer regular (per-test) fixtures for test isolation and proper resource management; use `#[once]` only for expensive, read-only, and safely static resources.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared as a static reference across all tests, but such fixtures are never dropped and cannot be async or generic.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared as a static reference across all tests, but such fixtures are never dropped and cannot be async or generic.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture argument in a test or another fixture, which is useful for destructuring or improving clarity.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Use the `#[from(original_fixture_name)]` attribute to rename a fixture when injecting it as an argument in a test or another fixture.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or improving argument clarity.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is especially useful when destructuring or for clarity.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Use the `#[from(original_fixture_name)]` attribute to rename injected fixture arguments in test or fixture functions
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use the `#[from(original_fixture_name)]` attribute to rename injected fixture arguments in test functions.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.727Z
Learning: Utilize features like `#[from]` for renaming and `#[default]`/`#[with]` for configurable fixtures to enhance clarity and reduce duplication
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: rstest can automatically convert string literals in #[case] or #[values] to types implementing std::str::FromStr, such as std::net::SocketAddr, simplifying test definitions.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest can automatically convert string literals to types implementing std::str::FromStr in #[case] or #[values] attributes, simplifying test definitions for types like SocketAddr.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest can automatically convert string literals in #[case] or #[values] to types implementing std::str::FromStr, simplifying test definitions for types like SocketAddr.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: Asynchronous fixtures and tests are supported by defining async fn fixtures and test functions. rstest integrates with async runtimes like async-std or tokio by combining #[rstest] with the runtime's test attribute.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: rstest supports asynchronous fixtures and tests by allowing async fn for both, and integrates with async runtimes like async-std or tokio by combining #[rstest] with the runtime's #[test] attribute.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest supports async fixtures and async test functions; it integrates with async runtimes like async-std or tokio by using the appropriate test attribute (e.g., #[tokio::test]) alongside #[rstest].
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: rstest supports async fixtures and async test functions; it integrates with async runtimes like async-std or tokio by combining #[rstest] with the appropriate runtime's #[test] attribute.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: rstest supports async fixtures and async test functions; it integrates with async runtimes like async-std or tokio by combining #[rstest] with the runtime's #[test] attribute.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: rstest supports asynchronous testing by allowing async fn fixtures and async test functions, integrating with async runtimes like async-std or tokio via their respective #[async_std::test] or #[tokio::test] attributes.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest supports asynchronous fixtures and tests by allowing async fn for both, and integrates with async runtimes like async-std or tokio by stacking the appropriate test attribute macro.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Define asynchronous fixtures as `async fn` and use them in async test functions with `#[rstest]`.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Write asynchronous tests as `async fn` functions annotated with `#[rstest]` and the appropriate async runtime attribute (e.g., `#[tokio::test]`, `#[async_std::test]`).
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Define asynchronous fixtures as `async fn` and annotate with `#[fixture]` for use in async rstest tests
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Annotate asynchronous test functions with both `#[rstest]` and the appropriate async runtime test attribute (e.g., `#[tokio::test]`, `#[async_std::test]`)
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Annotate asynchronous test functions with both `#[rstest]` and the appropriate async runtime attribute (e.g., `#[tokio::test]`, `#[async_std::test]`).
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The order of procedural macro attributes (e.g., #[rstest] and #[tokio::test]) can matter for correct async test execution; ensure the async runtime's test macro is correctly placed.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing the need for explicit impl Future types and automating .await insertion.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing the need for explicit impl Future types and automating .await calls.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use `#[future]` and `#[awt]` attributes to simplify handling of async fixtures and arguments in tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, preventing hangs from long-running or stalled operations. A global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, preventing hangs from long-running operations; a global timeout can be set with the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[timeout(...)] attribute in rstest sets a maximum execution time for async tests, preventing hangs from long-running or stalled operations. The RSTEST_TIMEOUT environment variable can set a default timeout for all async tests.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, preventing hangs; a global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, and a global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[timeout(...)] attribute in rstest sets a maximum execution time for async tests, and a global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[timeout(...)] attribute (and RSTEST_TIMEOUT environment variable) can be used to set a maximum execution time for async tests, preventing hangs.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `#[timeout(...)]` attribute to set a maximum execution time for asynchronous tests with `rstest`.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Set timeouts for async rstest tests using the `#[timeout(...)]` attribute or the `RSTEST_TIMEOUT` environment variable
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Apply the `#[timeout(...)]` attribute to async tests to set a maximum execution time and prevent hanging tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Temporary files and directories can be managed in rstest by using fixtures that return types like tempfile::TempDir, leveraging Rust's RAII for automatic cleanup after each test.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: For temporary files and directories, use fixtures that return types like tempfile::TempDir, leveraging Rust's RAII for automatic cleanup after each test.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Temporary files and directories should be managed via fixtures that return objects like tempfile::TempDir, leveraging Rust's RAII for automatic cleanup after each test. Avoid using #[once] for temporary resources to ensure proper cleanup.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Mocking external services (e.g., databases, HTTP APIs) is best encapsulated in fixtures, using crates like mockall or hand-rolled mocks, to keep test logic focused and maintainable.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[files("glob_pattern")] attribute in rstest parameterizes tests over files matching the pattern, injecting either PathBufs or file contents (with mode = "str" or "bytes"). This is powerful for data-driven testing but can increase binary size if embedding large files.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[files("glob_pattern")] attribute in rstest parameterizes tests over files matching a glob, injecting either their PathBuf or contents (as &str or &[u8]) into test arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: The #[files("glob_pattern")] attribute parameterizes tests over files matching a glob, injecting either PathBufs or file contents (with mode = "str" or "bytes") as arguments, enabling data-driven testing from the filesystem.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute on test arguments to inject file paths or contents matching a glob pattern for data-driven tests.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[files("glob_pattern")] attribute in rstest can parameterize tests over files matching a glob, injecting either file paths or file contents as test arguments.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute to inject file paths or contents as test arguments for data-driven tests.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute to inject file paths or contents as test arguments for data-driven tests.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute to inject file paths or contents as test arguments for data-driven testing.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.726Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute on test arguments to inject file paths or contents matching the glob pattern
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[files("glob_pattern")] attribute parameterizes tests over files matching a glob, injecting either PathBufs or file contents (as &str or &[u8]) into test arguments, and is useful for data-driven testing.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: Best practices for organizing rstest-based tests include: placing module-local fixtures in the module's tests submodule, sharing fixtures via a common module or crate, using descriptive names, composing small fixtures, and preferring per-test fixtures for isolation.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Best practices for organizing rstest-based tests include grouping related fixtures and tests into modules, using descriptive names, composing small focused fixtures, and preferring per-test fixtures for proper resource management.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Best practices for organizing fixtures and tests include: placing module-specific fixtures in the module's tests submodule, sharing fixtures via a common module or under #[cfg(test)] in the library, using clear naming conventions, composing small focused fixtures, and grouping related tests and fixtures into modules.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: Best practices for organizing fixtures and tests include: placing module-specific fixtures in the module's tests submodule, sharing fixtures via common modules or #[cfg(test)] in the library, using descriptive names, composing small fixtures, and grouping related tests and fixtures into modules.
Learnt from: CR
PR: leynos/wireframe#0
File: AGENTS.md:0-0
Timestamp: 2025-06-30T23:02:18.018Z
Learning: Applies to **/*_test.rs : Use `rstest` fixtures for shared setup.
Learnt from: CR
PR: leynos/netsuke#0
File: AGENTS.md:0-0
Timestamp: 2025-07-18T19:01:42.344Z
Learning: Applies to **/*_test.rs : Use rstest fixtures for shared setup.
Learnt from: CR
PR: leynos/ddlint#0
File: AGENTS.md:0-0
Timestamp: 2025-07-18T18:35:14.627Z
Learning: Applies to **/{tests,src}/**/*_test.rs : Use rstest fixtures for shared setup.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: rstest is most beneficial for complex setups, parameterized testing, and when aiming for readable, DRY, and maintainable test suites; for trivial tests, standard #[test] may suffice.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Use `rstest` for tests with complex setup, parameterization, or where improved readability and reduced boilerplate are desired; for simple unit tests, standard `#[test]` may suffice.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Prefer `rstest` for tests requiring complex setup, parameterization, or improved readability, and use standard `#[test]` for simple unit tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest-generated parameterized tests are named by appending ::case_N to the function name, which aids in identifying and running specific failing cases with cargo test.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest is not suitable for no_std environments, as it depends on the standard library and the test harness.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and test harness.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and test harness.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and test harness.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and the test harness.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and the test harness.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and the test harness.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The rstest-log crate helps integrate logging frameworks into rstest tests, ensuring proper log initialization for each test case.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The rstest-log crate can be used to ensure proper logging initialization in rstest tests, and the test-with crate can be combined with rstest to conditionally execute tests based on runtime conditions.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: For logging in rstest tests, the rstest-log crate can be used to ensure proper initialization of logging frameworks before each test runs.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `logtest` crate to verify log output in tests by capturing and asserting on emitted log records.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `rstest-log` crate to ensure logging frameworks are properly initialized in `rstest`-generated tests.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `rstest-log` crate to ensure logging frameworks are properly initialized in `rstest`-generated tests.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `logtest` crate to assert on log output in tests by starting a `Logger` before running the code under test.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Integrate logging in tests using the `rstest-log` crate to ensure proper log initialization in test cases.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/dependency-analysis.md:0-0
Timestamp: 2025-07-18T18:31:48.692Z
Learning: Applies to docs/{src,tests}/**/*_test.rs : logtest allows asserting on log output in unit tests
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The test-with crate can be combined with rstest to conditionally execute tests based on runtime conditions; macro order matters, with rstest generating test cases before test-with applies its logic.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.459Z
Learning: Applies to docs/**/*.rs : Use the `test-with` crate to conditionally execute tests based on runtime conditions, annotating after `#[rstest]`.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Conditional test execution (e.g., based on environment variables or file existence) can be achieved by combining rstest with the test-with crate, applying its attributes after rstest's macro expansion.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `test-with` crate to conditionally execute tests based on runtime conditions, applying its attributes after `#[rstest]`.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.328Z
Learning: Applies to docs/**/*.rs : Use the `test-with` crate to conditionally execute tests based on runtime conditions, applying its attributes after `#[rstest]`.
docs/netsuke-design.md (5)
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/**/Netsukefile : The 'foreach' entry in 'targets' allows dynamic generation of multiple targets via Jinja evaluation, producing a static build graph after rendering.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/src/ast.rs : The Rust structs representing the Netsukefile schema must be defined in 'src/ast.rs' and annotated with serde attributes for automatic deserialization.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/roadmap.md:0-0
Timestamp: 2025-07-18T19:04:19.373Z
Learning: Applies to docs/src/ast.rs : Implement the YAML parsing logic to deserialize a static Netsukefile into the NetsukeManifest AST.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/src/ast.rs : The 'StringOrList' enum in 'src/ast.rs' must use #[serde(untagged)] to allow fields to accept either a single string or a list of strings.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/netsuke-design.md:0-0
Timestamp: 2025-07-18T19:03:39.409Z
Learning: Applies to docs/**/*.rs : The initial Jinja context for rendering the Netsukefile must be constructed from the 'vars' section of the manifest.
🪛 LanguageTool
docs/rust-testing-with-rstest-fixtures.md
[typographical] ~505-~505: The word ‘When’ starts a question. Add a question mark (“?”) at the end of the sentence.
Context: ...onfigured_item(20, "item_".to_string())`. This hierarchical dependency resolution...
(WRB_QUESTION_MARK)
[style] ~564-~564: Consider a more descriptive alternative.
Context: ...s for Clarity: The #[from] Attribute Sometimes a fixture's function name might be long...
(SOMETIMES_OCCASIONALLY)
[uncategorized] ~592-~592: Use ‘wants’ only when referring to the third person singular such as “he wants”.
Context: ...the test only cares about some parts or wants to use more idiomatic names for destruc...
(CONFUSION_BETWEEN_NNS_OR_WANTS_TO)
[uncategorized] ~1015-~1015: The preposition ‘as’ seems more likely in this position.
Context: ...` attribute. This attribute can be used on a test function argument to inject file...
(AI_HYDRA_LEO_REPLACE_ON_AS)
[duplication] ~1224-~1224: Possible typo: you repeated a word.
Context: ...and running specific failing cases with cargo test test_function_name::case_N. Some IDEs or de...
(ENGLISH_WORD_REPEAT_RULE)
docs/netsuke-design.md
[style] ~258-~258: Consider using a more formal/concise alternative here.
Context: ...shlex/latest/shlex/). Any interpolation other than ins or outs is automatically shel...
(OTHER_THAN)
[uncategorized] ~317-~317: Loose punctuation mark.
Context: ...ses when kind is omitted. - sources: The input files required by the command...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~656-~656: Loose punctuation mark.
Context: ...quirement: &str) -> Result<bool, Error>`: An example of a domain-specific helpe...
(UNLIKELY_OPENING_PUNCTUATION)
[grammar] ~660-~660: Please add a punctuation mark at the end of paragraph.
Context: ...::Command19, parse the output using the semver` crate 4, and compare it aga...
(PUNCTUATION_PARAGRAPH_END)
[style] ~689-~689: Consider using the typographical ellipsis character here instead.
Context: ...owerful but often opaque functions like $(shell...) and $(wildcard...). Netsuke achieve...
(ELLIPSIS)
[style] ~690-~690: Consider using the typographical ellipsis character here instead.
Context: ...opaque functions like $(shell...) and $(wildcard...). Netsuke achieves and surpasses this ...
(ELLIPSIS)
[style] ~1263-~1263: Would you like to use the Oxford spelling “Visualizing”? The spelling ‘Visualising’ is also correct.
Context: ...l` using an embedded Dagre.js viewer. Visualising the graph is invaluable for understandi...
(OXFORD_SPELLING_Z_NOT_S)
[grammar] ~1268-~1268: An apostrophe ‘s’ denotes possession. Did you mean to use the plural form of the noun (no apostrophe)?
Context: ...Decisions The CLI is implemented using clap's derive API in src/cli.rs. Clap's `def...
(NOUN_APOSTROPHE_S_VERB)
[style] ~1307-~1307: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ile generator (ninja_gen.rs). 1. Implement the std::process::Command logic to in...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~1329-~1329: Consider using the typographical ellipsis character here instead.
Context: ... 1. Implement basic Jinja control flow ({% if... %}, {% for... %}) and variabl...
(ELLIPSIS)
[style] ~1329-~1329: Consider using the typographical ellipsis character here instead.
Context: ...asic Jinja control flow ({% if... %}, {% for... %}) and variable substitution. ...
(ELLIPSIS)
🔇 Additional comments (1)
docs/netsuke-design.md (1)
6-21: Introduction reads cleanly after re-wrap.The reformatted paragraph obeys 80-column wrapping, retains en-GB spelling, and avoids disallowed pronouns. No issues found.
Owner
Author
|
@coderabbitai review |
Contributor
✅ Actions performedReview triggered.
|
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🔭 Outside diff range comments (1)
docs/rust-testing-with-rstest-fixtures.md (1)
618-650: Fix example so it compiles
user_fixturerequires a mandatorynameargument yettest_default_userandtest_custom_name_userinject the fixture without overriding this parameter. The sample will not compile as written. Provide a default fornameand apply an explicit#[with]in the selective-override test.@@ #[fixture] fn user_fixture( - name: &str, + #[default("DefaultUser")] name: &str, #[default(30)] age: u8, #[default("Viewer")] role: &str, ) -> User { @@ #[rstest] -fn test_default_user(user_fixture: User) { +fn test_default_user(user_fixture: User) { @@ #[rstest] -fn test_admin_user(#[with("AdminUser", 42, "Admin")] user_fixture: User) { +fn test_admin_user(#[with("AdminUser", 42, "Admin")] user_fixture: User) { @@ #[rstest] -fn test_custom_name_user(user_fixture: User) { +fn test_custom_name_user(#[with("SpecificName")] user_fixture: User) {
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (3)
docs/behavioural-testing-in-rust-with-cucumber.md(1 hunks)docs/netsuke-design.md(40 hunks)docs/rust-testing-with-rstest-fixtures.md(36 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.md
Instructions used from:
Sources:
⚙️ CodeRabbit Configuration File
🧠 Learnings (1)
docs/rust-testing-with-rstest-fixtures.md (147)
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: In Rust, the rstest crate provides a declarative, macro-based approach to fixture-based and parameterized testing, reducing boilerplate and improving test readability.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: In Rust, the rstest crate enables declarative fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], which inject dependencies as function arguments, improving readability and reducing boilerplate.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], allowing dependencies to be injected as function arguments for improved readability and reduced boilerplate.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros such as #[rstest] and #[fixture], allowing for declarative test setup and dependency injection.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: In Rust, the rstest crate enables declarative fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], which inject dependencies as function arguments and generate multiple test cases from a single function.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], which inject dependencies into test functions by matching argument names to fixture functions.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: In Rust, the rstest crate enables fixture-based and parameterized testing using procedural macros like #[rstest] and #[fixture], allowing dependencies to be injected into test functions as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: Compared to standard Rust #[test], rstest provides declarative fixture injection and parameterization, reducing boilerplate and improving test clarity, especially for complex setups and input combinations.
Learnt from: CR
PR: leynos/lille#0
File: docs/testing-declarative-game-logic-in-dbsp.md:0-0
Timestamp: 2025-07-07T22:05:39.651Z
Learning: Applies to docs/{tests/**/*.{rs},**/*_test.rs} : Use the rstest crate to create reusable, composable test setups (fixtures) for both unit and BDD tests.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that encapsulate setup logic and can return any valid Rust type, including primitives, structs, or trait objects. Fixtures can depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that encapsulate setup logic and can return any valid Rust type, including primitives, structs, or trait objects. Fixtures can depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: rstest is most beneficial for complex setups, parameterized testing, and when aiming for readable, DRY, and maintainable test suites; for simple unit tests, standard #[test] may suffice.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.471Z
Learning: Applies to docs/**/Cargo.toml : Add `tokio` with `test-util` feature as a development dependency in `Cargo.toml` when using Tokio's test utilities.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that provide setup data or resources for tests. They can return any valid Rust type and can depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Fixtures in rstest are regular Rust functions annotated with #[fixture] and can return any valid Rust type, including primitives, structs, or trait objects. Fixtures can also depend on other fixtures by listing them as arguments.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: Fixtures in rstest are regular Rust functions annotated with #[fixture]; their return values are injected into tests by matching argument names, promoting separation of setup and test logic.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: Fixtures in rstest are regular Rust functions annotated with #[fixture]; their return values are injected into test functions by matching argument names, promoting test readability and reusability.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: Fixtures in rstest are Rust functions annotated with #[fixture] that encapsulate setup logic and can return any valid Rust type, including primitives, structs, or trait objects.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Define fixtures in Rust by annotating functions with `#[fixture]` from the `rstest` crate.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Define fixtures for test setup by annotating Rust functions with `#[fixture]` from the rstest crate.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.471Z
Learning: Applies to docs/**/*.rs : Define fixtures by annotating Rust functions with `#[fixture]` from the `rstest` crate.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest resolves fixture injection by argument name in the test function signature, following Rust's standard name resolution rules. Careful naming is required to avoid ambiguity when multiple fixtures with the same name are in scope.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: rstest resolves fixture injection by matching argument names in the test function to fixture function names, following Rust's standard name resolution rules. Careful naming is required to avoid ambiguity.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest injects fixtures into test functions by matching argument names to fixture function names, following Rust's standard name resolution rules.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: By default, rstest creates a new instance of a fixture for each test that uses it, ensuring test isolation and preventing shared mutable state between tests.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: By default, rstest creates a new instance of each fixture for every test that uses it, ensuring test isolation and preventing shared mutable state between tests.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: By default, rstest creates a new instance of each fixture for every test that uses it, ensuring test isolation and preventing shared mutable state between tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: By default, rstest creates a new instance of a fixture for each test that uses it, ensuring test isolation and preventing state leakage between tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: By default, rstest creates a new instance of each fixture for every test that uses it, ensuring test isolation and preventing state leakage between tests.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios (each case generates a separate test) and #[values(...)] for combinatorial testing (generating the Cartesian product of values for arguments).
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios (specific input/output pairs) and #[values(...)] for combinatorial testing (Cartesian product of argument values), generating individual test cases for each combination.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: Parameterized tests in rstest are created using #[case(...)] for table-driven scenarios and #[values(...)] for combinatorial testing, generating individual test cases for each set or combination of inputs.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios and #[values(...)] for combinatorial (Cartesian product) testing, generating individual test cases for each combination.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: Parameterized tests in rstest use #[case(...)] for table-driven scenarios and #[values(...)] for combinatorial (Cartesian product) testing, generating individual test cases for each combination.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[case(...)] attribute in rstest enables table-driven tests by generating a separate test for each case, with clear reporting for individual failures.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[case(...)] attribute in rstest allows table-driven tests by generating a separate test for each set of input arguments, with each case reported individually by the test runner.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Fixtures and parameterized arguments (#[case], #[values]) can be combined in the same rstest test function, allowing for expressive and comprehensive test scenarios.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: Fixtures and parameterized arguments (#[case], #[values]) can be combined in the same rstest test function, allowing for expressive and flexible test scenarios.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `#[case(...)]` attribute in `#[rstest]` tests to define table-driven, parameterized test cases.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[values(...)] attribute in rstest generates tests for every combination of provided values (Cartesian product), which can lead to a combinatorial explosion in the number of tests if not used judiciously.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[values(...)] attribute in rstest enables combinatorial testing by generating tests for every possible combination of provided values across arguments, which can lead to a combinatorial explosion if not used judiciously.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `#[values(...)]` attribute in `#[rstest]` tests to generate tests for all combinations of provided values (combinatorial testing).
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.471Z
Learning: Applies to docs/**/*.rs : Use the `#[values(...)]` attribute on test function arguments to generate combinatorial test cases with `rstest`.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Combine fixtures and parameterized arguments (`#[case]` or `#[values]`) in the same `#[rstest]` test function for expressive test scenarios.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.471Z
Learning: Applies to docs/**/*.rs : Combine fixtures and parameterized arguments (`#[case]` or `#[values]`) in the same test function for expressive test scenarios.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Combine fixtures and parameterized arguments (`#[case]`, `#[values]`) in the same test function to test variable scenarios within a consistent setup.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Use #[once] fixtures sparingly and only for expensive, read-only, and safely static resources, as their values are never dropped and may cause resource leaks if used for temporary or cleanup-requiring resources.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared across all tests, but the returned value is promoted to 'static' lifetime and is never dropped, making it suitable only for passive or OS-managed resources.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared across all tests, but the returned value is never dropped (static lifetime), making it suitable only for passive or OS-managed resources.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: Use #[once] fixtures only for expensive, read-only, and safely static resources, as they are never dropped and can lead to resource leaks if misused.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: Prefer regular (per-test) fixtures for resources that require cleanup or test isolation; use #[once] only for expensive, read-only, and truly static resources.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared across all tests, but the returned value is never dropped, making it suitable only for static, read-only resources.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared as a static reference across all tests, but such fixtures are never dropped and cannot be async or generic.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared as a static reference across all tests, but such fixtures are never dropped and cannot be async or generic.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared as a static reference across all tests, but such fixtures are never dropped and cannot be async or generic.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[once] attribute on a fixture causes it to be initialized only once and shared as a static reference across all tests, but such fixtures are never dropped and cannot be async or generic.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture argument in a test or another fixture, which is useful for destructuring or improving clarity.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or improving argument clarity.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Use the `#[from(original_fixture_name)]` attribute to rename a fixture when injecting it as an argument in a test or another fixture.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is especially useful when destructuring or for clarity.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.739Z
Learning: Applies to docs/**/*.rs : Use the `#[from(original_fixture_name)]` attribute to rename injected fixture arguments in test or fixture functions
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[from(original_fixture_name)] attribute allows renaming a fixture when injecting it into a test or another fixture, which is useful for destructuring or clarity.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.739Z
Learning: Utilize features like `#[from]` for renaming and `#[default]`/`#[with]` for configurable fixtures to enhance clarity and reduce duplication
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: rstest can automatically convert string literals in #[case] or #[values] to types implementing std::str::FromStr, such as std::net::SocketAddr, simplifying test definitions.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest can automatically convert string literals to types implementing std::str::FromStr in #[case] or #[values] attributes, simplifying test definitions for types like SocketAddr.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest can automatically convert string literals in #[case] or #[values] to types implementing std::str::FromStr, simplifying test definitions for types like SocketAddr.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: Asynchronous fixtures and tests are supported by defining async fn fixtures and test functions. rstest integrates with async runtimes like async-std or tokio by combining #[rstest] with the runtime's test attribute.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: rstest supports asynchronous fixtures and tests by allowing async fn for both, and integrates with async runtimes like async-std or tokio by combining #[rstest] with the runtime's #[test] attribute.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest supports async fixtures and async test functions; it integrates with async runtimes like async-std or tokio by using the appropriate test attribute (e.g., #[tokio::test]) alongside #[rstest].
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: rstest supports async fixtures and async test functions; it integrates with async runtimes like async-std or tokio by combining #[rstest] with the appropriate runtime's #[test] attribute.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: rstest supports async fixtures and async test functions; it integrates with async runtimes like async-std or tokio by combining #[rstest] with the runtime's #[test] attribute.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: rstest supports asynchronous testing by allowing async fn fixtures and async test functions, integrating with async runtimes like async-std or tokio via their respective #[async_std::test] or #[tokio::test] attributes.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest supports asynchronous fixtures and tests by allowing async fn for both, and integrates with async runtimes like async-std or tokio by stacking the appropriate test attribute macro.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Define asynchronous fixtures as `async fn` and use them in async test functions with `#[rstest]`.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.379Z
Learning: Applies to docs/**/*.rs : Write asynchronous tests as `async fn` functions annotated with `#[rstest]` and the appropriate async runtime attribute (e.g., `#[tokio::test]`, `#[async_std::test]`).
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.739Z
Learning: Applies to docs/**/*.rs : Annotate asynchronous test functions with both `#[rstest]` and the appropriate async runtime test attribute (e.g., `#[tokio::test]`, `#[async_std::test]`)
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.471Z
Learning: Applies to docs/**/*.rs : Annotate asynchronous test functions with both `#[rstest]` and the appropriate async runtime attribute (e.g., `#[tokio::test]`, `#[async_std::test]`).
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The order of procedural macro attributes (e.g., #[rstest] and #[tokio::test]) can matter for correct async test execution; ensure the async runtime's test macro is correctly placed.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing the need for explicit impl Future types and automating .await insertion.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.857Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing the need for explicit impl Future types and automating .await calls.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[future] and #[awt] attributes in rstest simplify working with async fixtures and arguments by removing boilerplate and optionally auto-awaiting futures.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.379Z
Learning: Applies to docs/**/*.rs : Use `#[future]` and `#[awt]` attributes to simplify handling of async fixtures and arguments in tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The order of procedural macro attributes matters when stacking rstest with async runtime macros or conditional test execution macros (e.g., test-with); rstest should typically be applied first to generate the test cases.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, preventing hangs from long-running or stalled operations. A global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, preventing hangs from long-running operations; a global timeout can be set with the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[timeout(...)] attribute in rstest sets a maximum execution time for async tests, preventing hangs from long-running or stalled operations. The RSTEST_TIMEOUT environment variable can set a default timeout for all async tests.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, preventing hangs; a global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[timeout(...)] attribute sets a maximum execution time for async tests, and a global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[timeout(...)] attribute in rstest sets a maximum execution time for async tests, and a global timeout can be set via the RSTEST_TIMEOUT environment variable.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[timeout(...)] attribute (and RSTEST_TIMEOUT environment variable) can be used to set a maximum execution time for async tests, preventing hangs.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.471Z
Learning: Applies to docs/**/*.rs : Use the `#[timeout(...)]` attribute to set a maximum execution time for asynchronous tests with `rstest`.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.739Z
Learning: Applies to docs/**/*.rs : Set timeouts for async rstest tests using the `#[timeout(...)]` attribute or the `RSTEST_TIMEOUT` environment variable
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Apply the `#[timeout(...)]` attribute to async tests to enforce a maximum execution time and prevent hanging tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Temporary files and directories can be managed in rstest by using fixtures that return types like tempfile::TempDir, leveraging Rust's RAII for automatic cleanup after each test.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: For temporary files and directories, use fixtures that return types like tempfile::TempDir, leveraging Rust's RAII for automatic cleanup after each test.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Temporary files and directories should be managed via fixtures that return objects like tempfile::TempDir, leveraging Rust's RAII for automatic cleanup after each test. Avoid using #[once] for temporary resources to ensure proper cleanup.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: Use regular (per-test) fixtures for resources that require cleanup or test isolation, and reserve #[once] fixtures for expensive, read-only, and static resources.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Mocking external services (e.g., databases, HTTP APIs) is best encapsulated in fixtures, using crates like mockall or hand-rolled mocks, to keep test logic focused and maintainable.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: The #[files("glob_pattern")] attribute in rstest parameterizes tests over files matching the pattern, injecting either PathBufs or file contents (with mode = "str" or "bytes"). This is powerful for data-driven testing but can increase binary size if embedding large files.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: The #[files("glob_pattern")] attribute in rstest parameterizes tests over files matching a glob, injecting either their PathBuf or contents (as &str or &[u8]) into test arguments.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: The #[files("glob_pattern")] attribute parameterizes tests over files matching a glob, injecting either PathBufs or file contents (with mode = "str" or "bytes") as arguments, enabling data-driven testing from the filesystem.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute on test arguments to inject file paths or contents matching a glob pattern for data-driven tests.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: The #[files("glob_pattern")] attribute in rstest can parameterize tests over files matching a glob, injecting either file paths or file contents as test arguments.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T21:21:37.739Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute on test arguments to inject file paths or contents matching the glob pattern
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `#[files("glob_pattern")]` attribute to inject file paths or contents as test arguments for data-driven testing.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: The #[files("glob_pattern")] attribute parameterizes tests over files matching a glob, injecting either PathBufs or file contents (as &str or &[u8]) into test arguments, and is useful for data-driven testing.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The #[files("glob_pattern")] attribute parameterizes tests over files matching a glob, injecting either their PathBuf or contents (as &str or &[u8]) into test arguments.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The #[files("glob_pattern")] attribute parameterizes tests over files matching a glob pattern, injecting either file paths or contents, and supports modes like str or bytes for content injection.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: Best practices for organizing rstest-based tests include: placing module-local fixtures in the module's tests submodule, sharing fixtures via a common module or crate, using descriptive names, composing small fixtures, and preferring per-test fixtures for isolation.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Best practices for organizing rstest-based tests include grouping related fixtures and tests into modules, using descriptive names, composing small focused fixtures, and preferring per-test fixtures for proper resource management.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: Best practices for organizing fixtures and tests include: placing module-specific fixtures in the module's tests submodule, sharing fixtures via a common module or under #[cfg(test)] in the library, using clear naming conventions, composing small focused fixtures, and grouping related tests and fixtures into modules.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: Best practices for organizing fixtures and tests include: placing module-specific fixtures in the module's tests submodule, sharing fixtures via common modules or #[cfg(test)] in the library, using descriptive names, composing small fixtures, and grouping related tests and fixtures into modules.
Learnt from: CR
PR: leynos/wireframe#0
File: AGENTS.md:0-0
Timestamp: 2025-06-30T23:02:18.018Z
Learning: Applies to **/*_test.rs : Use `rstest` fixtures for shared setup.
Learnt from: CR
PR: leynos/netsuke#0
File: AGENTS.md:0-0
Timestamp: 2025-07-18T19:01:42.365Z
Learning: Applies to **/*_test.rs : Use rstest fixtures for shared setup.
Learnt from: CR
PR: leynos/ddlint#0
File: AGENTS.md:0-0
Timestamp: 2025-07-18T18:35:14.639Z
Learning: Applies to **/{tests,src}/**/*_test.rs : Use rstest fixtures for shared setup.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: rstest is most beneficial for complex setups, parameterized testing, and when aiming for readable, DRY, and maintainable test suites; for trivial tests, standard #[test] may suffice.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-07T22:05:30.492Z
Learning: Use `rstest` for tests with complex setup, parameterization, or where improved readability and reduced boilerplate are desired; for simple unit tests, standard `#[test]` may suffice.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Prefer `rstest` for tests requiring complex setup, parameterization, or improved readability, and use standard `#[test]` for simple unit tests.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest-generated parameterized tests are named by appending ::case_N to the function name, which aids in identifying and running specific failing cases with cargo test.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:09.111Z
Learning: rstest is not suitable for no_std environments, as it depends on the standard library and the test harness.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and test harness.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and test harness.
Learnt from: CR
PR: leynos/mxd#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T23:40:48.640Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and test harness.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:36.858Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and the test harness.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and the test harness.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-26T00:20:29.033Z
Learning: rstest is not suitable for no_std environments, as it relies on the standard library and the test harness.
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The rstest-log crate helps integrate logging frameworks into rstest tests, ensuring proper log initialization for each test case.
Learnt from: CR
PR: leynos/mdtablefix#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T23:09:41.600Z
Learning: The rstest-log crate can be used to ensure proper logging initialization in rstest tests, and the test-with crate can be combined with rstest to conditionally execute tests based on runtime conditions.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: For logging in rstest tests, the rstest-log crate can be used to ensure proper initialization of logging frameworks before each test runs.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.471Z
Learning: Applies to docs/**/*.rs : Use the `logtest` crate to verify log output in tests by capturing and asserting on emitted log records.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.471Z
Learning: Applies to docs/**/*.rs : Use the `rstest-log` crate to ensure logging frameworks are properly initialized in `rstest`-generated tests.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `rstest-log` crate to ensure logging frameworks are properly initialized in `rstest`-generated tests.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `logtest` crate to assert on log output in tests by starting a `Logger` before running the code under test.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.379Z
Learning: Applies to docs/**/*.rs : Integrate logging in tests using the `rstest-log` crate to ensure proper log initialization in test cases.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/dependency-analysis.md:0-0
Timestamp: 2025-07-18T18:31:48.721Z
Learning: Applies to docs/{src,tests}/**/*_test.rs : logtest allows asserting on log output in unit tests
Learnt from: CR
PR: leynos/lille#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-24T18:32:30.955Z
Learning: The test-with crate can be combined with rstest to conditionally execute tests based on runtime conditions; macro order matters, with rstest generating test cases before test-with applies its logic.
Learnt from: CR
PR: leynos/netsuke#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T19:05:14.471Z
Learning: Applies to docs/**/*.rs : Use the `test-with` crate to conditionally execute tests based on runtime conditions, annotating after `#[rstest]`.
Learnt from: CR
PR: leynos/femtologging#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-25T00:05:37.557Z
Learning: Conditional test execution (e.g., based on environment variables or file existence) can be achieved by combining rstest with the test-with crate, applying its attributes after rstest's macro expansion.
Learnt from: CR
PR: leynos/wireframe#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-06-30T23:08:10.890Z
Learning: Applies to docs/**/*.rs : Use the `test-with` crate to conditionally execute tests based on runtime conditions, applying its attributes after `#[rstest]`.
Learnt from: CR
PR: leynos/ddlint#0
File: docs/rust-testing-with-rstest-fixtures.md:0-0
Timestamp: 2025-07-18T18:40:11.379Z
Learning: Applies to docs/**/*.rs : Use the `test-with` crate to conditionally execute tests based on runtime conditions, applying its attributes after `#[rstest]`.
🪛 LanguageTool
docs/rust-testing-with-rstest-fixtures.md
[typographical] ~505-~505: The word ‘When’ starts a question. Add a question mark (“?”) at the end of the sentence.
Context: ...onfigured_item(20, "item_".to_string())`. This hierarchical dependency resolution...
(WRB_QUESTION_MARK)
[style] ~564-~564: Consider a more descriptive alternative.
Context: ...s for Clarity: The #[from] Attribute Sometimes a fixture's function name might be long...
(SOMETIMES_OCCASIONALLY)
[uncategorized] ~592-~592: Use ‘wants’ only when referring to the third person singular such as “he wants”.
Context: ...the test only cares about some parts or wants to use more idiomatic names for destruc...
(CONFUSION_BETWEEN_NNS_OR_WANTS_TO)
[uncategorized] ~1015-~1015: The preposition ‘as’ seems more likely in this position.
Context: ...` attribute. This attribute can be used on a test function argument to inject file...
(AI_HYDRA_LEO_REPLACE_ON_AS)
[duplication] ~1224-~1224: Possible typo: you repeated a word.
Context: ...and running specific failing cases with cargo test test_function_name::case_N. Some IDEs or de...
(ENGLISH_WORD_REPEAT_RULE)
docs/netsuke-design.md
[style] ~258-~258: Consider using a more formal/concise alternative here.
Context: ...shlex/latest/shlex/). Any interpolation other than ins or outs is automatically shel...
(OTHER_THAN)
[uncategorized] ~317-~317: Loose punctuation mark.
Context: ...ses when kind is omitted. - sources: The input files required by the command...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~656-~656: Loose punctuation mark.
Context: ...quirement: &str) -> Result<bool, Error>`: An example of a domain-specific helpe...
(UNLIKELY_OPENING_PUNCTUATION)
[grammar] ~660-~660: Please add a punctuation mark at the end of paragraph.
Context: ...::Command19, parse the output using the semver` crate 4, and compare it aga...
(PUNCTUATION_PARAGRAPH_END)
[style] ~689-~689: Consider using the typographical ellipsis character here instead.
Context: ...owerful but often opaque functions like $(shell...) and $(wildcard...). Netsuke achieve...
(ELLIPSIS)
[style] ~690-~690: Consider using the typographical ellipsis character here instead.
Context: ...opaque functions like $(shell...) and $(wildcard...). Netsuke achieves and surpasses this ...
(ELLIPSIS)
[style] ~1263-~1263: Would you like to use the Oxford spelling “Visualizing”? The spelling ‘Visualising’ is also correct.
Context: ...l` using an embedded Dagre.js viewer. Visualising the graph is invaluable for understandi...
(OXFORD_SPELLING_Z_NOT_S)
[grammar] ~1268-~1268: An apostrophe ‘s’ denotes possession. Did you mean to use the plural form of the noun (no apostrophe)?
Context: ...Decisions The CLI is implemented using clap's derive API in src/cli.rs. Clap's `def...
(NOUN_APOSTROPHE_S_VERB)
[style] ~1307-~1307: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ile generator (ninja_gen.rs). 1. Implement the std::process::Command logic to in...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~1329-~1329: Consider using the typographical ellipsis character here instead.
Context: ... 1. Implement basic Jinja control flow ({% if... %}, {% for... %}) and variabl...
(ELLIPSIS)
[style] ~1329-~1329: Consider using the typographical ellipsis character here instead.
Context: ...asic Jinja control flow ({% if... %}, {% for... %}) and variable substitution. ...
(ELLIPSIS)
🔇 Additional comments (3)
docs/behavioural-testing-in-rust-with-cucumber.md (1)
936-945: List renumbering and wrapping now comply with guidelinesMaintain the current form. Ordered list ascends correctly, redundant MD029 suppression is gone, line lengths sit < 80 cols, and no 2nd-person pronouns slipped in.
docs/netsuke-design.md (2)
6-8: No issues spottedThe re-phrased introduction stays within the 80-column limit, keeps Oxford commas, and avoids 1st/2nd-person pronouns.
56-60: No issues spottedThe re-wrapped paragraph now breaks cleanly at ≤80 columns and retains British spelling.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (1)
docs/netsuke-design.md(48 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
docs/**/*.md
Instructions used from:
Sources:
📄 CodeRabbit Inference Engine
- AGENTS.md
**/*.md
Instructions used from:
Sources:
📄 CodeRabbit Inference Engine
- AGENTS.md
⚙️ CodeRabbit Configuration File
🪛 LanguageTool
docs/netsuke-design.md
[style] ~258-~258: Consider using a more formal/concise alternative here.
Context: ...shlex/latest/shlex/). Any interpolation other than ins or outs is automatically shel...
(OTHER_THAN)
[uncategorized] ~317-~317: Loose punctuation mark.
Context: ...ses when kind is omitted. - sources: The input files required by the command...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~656-~656: Loose punctuation mark.
Context: ...quirement: &str) -> Result<bool, Error>`: An example of a domain-specific helpe...
(UNLIKELY_OPENING_PUNCTUATION)
[grammar] ~660-~660: Please add a punctuation mark at the end of paragraph.
Context: ...::Command19, parse the output using the semver` crate 4, and compare it aga...
(PUNCTUATION_PARAGRAPH_END)
[style] ~689-~689: Consider using the typographical ellipsis character here instead.
Context: ...owerful but often opaque functions like $(shell...) and $(wildcard...). Netsuke achieve...
(ELLIPSIS)
[style] ~690-~690: Consider using the typographical ellipsis character here instead.
Context: ...opaque functions like $(shell...) and $(wildcard...). Netsuke achieves and surpasses this ...
(ELLIPSIS)
[style] ~1148-~1148: Consider using the typographical ellipsis character here instead.
Context: ...nction where the error occurred returns Err(IrGenError::RuleNotFound {... }.into()). The .into() call converts...
(ELLIPSIS)
[grammar] ~1276-~1276: An apostrophe ‘s’ denotes possession. Did you mean to use the plural form of the noun (no apostrophe)?
Context: ...Decisions The CLI is implemented using clap's derive API in src/cli.rs. Clap's `def...
(NOUN_APOSTROPHE_S_VERB)
[style] ~1315-~1315: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ile generator (ninja_gen.rs). 1. Implement the std::process::Command logic to in...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~1337-~1337: Consider using the typographical ellipsis character here instead.
Context: ... 1. Implement basic Jinja control flow ({% if... %}, {% for... %}) and variabl...
(ELLIPSIS)
[style] ~1337-~1337: Consider using the typographical ellipsis character here instead.
Context: ...asic Jinja control flow ({% if... %}, {% for... %}) and variable substitution. ...
(ELLIPSIS)
[typographical] ~1430-~1430: To join two clauses or introduce examples, consider using an em dash.
Context: ...uild.org/> [^2]: Ninja (build system) - Wikipedia, accessed on July 12, 2025, <...
(DASH_RULE)
[typographical] ~1433-~1433: To join two clauses or introduce examples, consider using an em dash.
Context: ...Complete Guide To The Ninja Build System - Spectra - Mathpix, accessed on July 12, ...
(DASH_RULE)
[typographical] ~1433-~1433: To join two clauses or introduce examples, consider using an em dash.
Context: ...uide To The Ninja Build System - Spectra - Mathpix, accessed on July 12, 2025, <<<...
(DASH_RULE)
[typographical] ~1437-~1437: To join two clauses or introduce examples, consider using an em dash.
Context: ...-the-ninja-build-system> [^4]: semver - Rust, accessed on July 12, 2025, <<http...
(DASH_RULE)
[typographical] ~1440-~1440: To join two clauses or introduce examples, consider using an em dash.
Context: ...io/Agents/semver/index.html> Versioning - GitHub, accessed on July 12, 2025, <<<h...
(DASH_RULE)
[typographical] ~1446-~1446: To join two clauses or introduce examples, consider using an em dash.
Context: ...latest/semver/> [^7]: How Ninja works - Fuchsia, accessed on July 12, 2025, <ht...
(DASH_RULE)
[typographical] ~1454-~1454: To join two clauses or introduce examples, consider using an em dash.
Context: .../34ebqOUxnXg> [^11]: Saphyr libraries - crates.io: Rust Pack...
(DASH_RULE)
[typographical] ~1463-~1463: To join two clauses or introduce examples, consider using an em dash.
Context: ...ps://docs.rs/saphyr> [^15]: minijinja - crates.io: Rust Pack...
(DASH_RULE)
[typographical] ~1466-~1466: To join two clauses or introduce examples, consider using an em dash.
Context: ...io/crates/minijinja> [^16]: minijinja - Rust - Docs.rs, access...
(DASH_RULE)
[typographical] ~1466-~1466: To join two clauses or introduce examples, consider using an em dash.
Context: ...es/minijinja> [^16]: minijinja - Rust - Docs.rs, accessed on J...
(DASH_RULE)
[typographical] ~1469-~1469: To join two clauses or introduce examples, consider using an em dash.
Context: .../docs.rs/minijinja/> [^17]: minijinja - Rust, accessed on July 12, 2025, <<http...
(DASH_RULE)
[typographical] ~1482-~1482: To join two clauses or introduce examples, consider using an em dash.
Context: ...ck-python-version> [^22]: shell_quote - Rust - Docs.rs, access...
(DASH_RULE)
[typographical] ~1482-~1482: To join two clauses or introduce examples, consider using an em dash.
Context: ...on-version> [^22]: shell_quote - Rust - Docs.rs, accessed on J...
(DASH_RULE)
[typographical] ~1488-~1488: To join two clauses or introduce examples, consider using an em dash.
Context: ...ocess/index.html> [^24]: std::process - Rust, accessed on July 12, 2025, <<http...
(DASH_RULE)
[typographical] ~1499-~1499: To join two clauses or introduce examples, consider using an em dash.
Context: ...-vs-snafu-2003> and Advanced Techniques - Technorely, accessed on July 12, 2025, ...
(DASH_RULE)
[typographical] ~1503-~1503: To join two clauses or introduce examples, consider using an em dash.
Context: ...ractical guide to Error Handling in Rust - Dev State, accessed on July 12, 2025, <h...
(DASH_RULE)
[typographical] ~1506-~1506: To join two clauses or introduce examples, consider using an em dash.
Context: ...andling/> [^30]: thiserror and anyhow - Comprehensive Rust, accessed on July 12,...
(DASH_RULE)
[typographical] ~1515-~1515: To join two clauses or introduce examples, consider using an em dash.
Context: ...in-rust> [^32]: Nicer error reporting - Command Line Applications in Rust, acces...
(DASH_RULE)
🔇 Additional comments (1)
docs/netsuke-design.md (1)
674-676: Hyphenation now correctThe stray space in “non-negotiable” is gone; wording aligns with en-GB-oxendict rules.
Comment on lines
+1221
to
1242
| struct Cli { /// Path to the Netsuke manifest file to use. | ||
| #[arg(short, long, value_name = "FILE", default_value = "Netsukefile")] | ||
| file: PathBuf, | ||
|
|
||
| /// Change to this directory before doing anything. | ||
| #[arg(short = 'C', long, value_name = "DIR")] | ||
| directory: Option<PathBuf>, | ||
|
|
||
| /// Set the number of parallel build jobs. | ||
| #[arg(short, long, value_name = "N")] | ||
| jobs: Option<usize>, | ||
|
|
||
| #[command(subcommand)] | ||
| command: Option<Commands>, | ||
| } | ||
| command: Option<Commands>, } | ||
|
|
||
| enum Commands { | ||
| /// Build specified targets (or default targets if none are given) [default]. | ||
| Build { | ||
| /// A list of specific targets to build. | ||
| targets: Vec<String>, | ||
| }, | ||
| #[derive(Subcommand)] | ||
| enum Commands { /// Build specified targets (or default targets if none are | ||
| given) [default]. Build { /// A list of specific targets to build. targets: | ||
| Vec<String>, }, | ||
|
|
||
| /// Remove build artifacts and intermediate files. | ||
| Clean {}, | ||
| /// Remove build artifacts and intermediate files. Clean {}, | ||
|
|
Contributor
There was a problem hiding this comment.
Fix the malformed Rust CLI snippet
The snippet still will not compile or render cleanly:
- The struct’s opening brace, doc-comment, and the closing brace for
Cliall sit on the same line. command: Option<Commands>, }mixes a field and a brace on one line.enum Commandscollapses multiple statements onto single lines and leaves trailing braces in comments.- The
Buildvariant’s documentation and field list are jumbled.
Patch the snippet so that every item occupies its own line and brace pairs are properly balanced.
-#[derive(Parser)]
-struct Cli { /// Path to the Netsuke manifest file to use.
+#[derive(Parser)]
+struct Cli {
+ /// Path to the Netsuke manifest file to use.
#[arg(short, long, value_name = "FILE", default_value = "Netsukefile")]
file: PathBuf,
@@
- #[command(subcommand)]
- command: Option<Commands>, }
+ #[command(subcommand)]
+ command: Option<Commands>,
+}
@@
-#[derive(Subcommand)]
-enum Commands { /// Build specified targets (or default targets if none are
-given) [default]. Build { /// A list of specific targets to build. targets:
-Vec<String>, },
-
- /// Remove build artifacts and intermediate files. Clean {},
+#[derive(Subcommand)]
+enum Commands {
+ /// Build specified targets (or default targets if none are given).
+ Build {
+ /// A list of specific targets to build.
+ targets: Vec<String>,
+ },
+
+ /// Remove build artifacts and intermediate files.
+ Clean {},
+
/// Display the build dependency graph in DOT format for visualization.
Graph {},
}Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In docs/netsuke-design.md around lines 1221 to 1242, the Rust CLI snippet is
malformed with braces and fields on the same lines and multiple statements
collapsed together. Fix this by placing the struct's opening brace,
doc-comments, and closing brace each on separate lines; separate the field
declaration and closing brace for the Cli struct onto different lines; expand
the enum Commands so each variant and its documentation are on their own lines
with properly balanced braces; and ensure the Build variant's documentation and
fields are clearly separated and formatted line-by-line.
This was referenced Jul 19, 2025
This was referenced Jul 20, 2025
This was referenced Jul 28, 2025
This was referenced Aug 10, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
make fmtto normalize MarkdownTesting
make lintmake testmake markdownlintmake nixiehttps://chatgpt.com/codex/tasks/task_e_687abbc353508322a4d65bef1a11c805
Summary by Sourcery
Documentation:
make fmtto normalize line wrapping, indentation, and spacing in all Markdown files