rusty-fork
rusty-fork copied to clipboard
AltSysrq
Run Rust tests in isolated subprocesses
This PR allow to use `rusty_fork_test!` tests having a return type : ```rust rusty_fork_test! { #[test] fn trivial() { } #[test] fn trivial_with_return() -> Result
Dedupes a crate in my dep tree 🙃 As far as I can tell, the only difference between quick-error 1.x and 2.x is that 2.x switched from generating the deprecated...
This just updates `quick-error` to version 2. This did involve switching `cause` over to `source` and removing `description` since both were deprecated since rust 1.33.0 and 1.42.0 respectively.
Implement proc macro alternative to `rusty_fork_test!`. Theres a bit of documentation missing and maybe more unit tests could help, I'm willing to do it, but would like some direction. Fixes...
Fixes #5. I also tried to fix #9, but I don't think its properly possible without a proc macro.
I am experimenting with your crate for testing my [cargo-wix](https://github.com/volks73/cargo-wix) subcommand. This would be for Windows and it most revolves around modifying the Current Working Directory (CWD) for each of...
The `rusty_fork_test!` macro does not accept `async fn`. I need to test some async functions that share global data structures. It would be very useful that this could be done...
``` use std::env; rusty_fork_test! { #[test] fn test_result() -> Result { let x = env::var("HOME")?; Ok(()) } } ``` error ``` error: no rules expected the token `->` --> myfile.rs...
One thing I've been using rusty-fork for is to test behavior connected to environment variables. (Thanks!) For example: ```rust rusty_fork_test! { #[test] fn resolve_auto_not_on_github() { env::remove_var("GITHUB_ACTION"); assert_eq!(AnnotationKind::Auto.resolve(), AnnotationKind::None); } #[test]...
