issues Search Results · repo:palfrey/serial_test language:Rust
Filter by
44 results
(80 ms)44 results
inpalfrey/serial_test (press backspace or delete to remove)In nightly it is possible to add benchmarks that take a Bencher as an argument. The serial proc macro does not support
this though.
#![feature(test)]
#[bench]
#[serial]
fn benchmark_with_bencher(bench: ...
raldone01
- 2
- Opened 8 days ago
- #127
The following test does not compile:
#[cfg(test)]
mod test {
use serial_test::serial;
#[test]
#[serial]
fn test() - Result Result (), () , () {
Ok(Ok(()))
}
}
Instead, ...
nilrem3
- 2
- Opened 8 days ago
- #126
#[serial_test(crate = wrapper::__derive_refs::serial)]
This is for proc-macros generating #[serial_test] annotations: they should rely on reexports of serial crate.
stepancheg
- 4
- Opened on Dec 31, 2024
- #123
Is it possible that [#serial] is not respected when using Tokio? I have a test definition as below (many in fact, which
should be run one at-a-time). Each test is resource intensive and should be run in ...
schulte-lukas
- 2
- Opened on Nov 4, 2024
- #121
This repo is using proc-macro2 v1.0.71 and this is causing the issue.
proc-macro-error is unmaintained and is updated to proc-macro-error2: https://github.com/jbaublitz/getset/issues/94
proc-macro2 v1.0.89 ...
vsirivol
- 2
- Opened on Nov 1, 2024
- #116
As part of the RoSctober Race presented by Race of Sloths, we recognized this repo to be highly valuable in the
open-source movement.
Existing and new contributors will be rewarded proportionally to their ...
race-of-sloths
- Opened on Sep 20, 2024
- #115
Background
I am using the crates rstest and serial_test.
VS Code s IntelliSense stops working when I define a test function with both #[rstest] and #[serial].
IntelliSense is a VS Code feature (or rather ...
mtilda
- 2
- Opened on Jun 18, 2024
- #112
It s kind of tedious to mark each test function with a macros. Is there a way to make all of the functions inside mod
tests { ... } serial?
xamgore
- 12
- Opened on Dec 30, 2023
- #103
the idea is to have multiple subsets for a single test:
#[test]
#[serial(redis)]
fn one() {}
#[test]
#[serial(s3)]
fn two() {}
#[test]
#[serial(redis,s3)]
fn three() {}
one and two can run concurrently, ...
zignis
- 2
- Opened on Dec 1, 2023
- #101
I m using the attribute #[serial] on my integration tests since I want them to follow a certain sequential order because
I can t currently think of any other way to solve my problem.
This is my structure ...
mjovanc
- 4
- Opened on Oct 8, 2023
- #100
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Restrict your search to the title by using the in:title qualifier.Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Press the /
key to activate the search input again and adjust your query.