You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry I was writing response to this issue 2 days ago and something distracted me so I've never pushed the comment button sorry 😞
This is a duplicate of #62
It's basically by design, running tests in isolation was a fix for skeptic tests leaving artifacts in the crate root in rust-cookbook.
I might consider providing a configuration switch to use crate PWD again. Would that be enough? I can't give an ETA on that one as my free time is pretty scarce these days but it's certainly on my radar!
From testing a lib perspective, I already need to keep the filesystem clean for normal tests and take the same approach for Skeptic tests. I can see the appeal of automatically running in a different directory though. it removes a major piece of boiler plate from documentation that would exist just for verifying the docs.
epage
changed the title
Skeptic tests not runnin in the same working directory as regular tests
Skeptic tests not running in the same working directory as regular tests
Nov 6, 2017
In assert_cli, we want to test
Assert::main_binary
but its implemented by callingcargo run
. This works for regular tests but can't for skeptic testsThe text was updated successfully, but these errors were encountered: