-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document that each test block returns to the original cwd? #100
Comments
It is indeed a side-effect, but It can also be a useful feature. I would be -Chad P.S. Whats your overall opinion of Fennec? Have you used these features yet: In Fennec::Declare this would be: On Tue, Apr 8, 2014 at 1:55 PM, Michael G. Schwern <notifications@github.com
|
I appreciate you don't have time to do it right now. On the off chance I need to shave this yak, would the I've only used The main downside I've encountered is the aforementioned forking makes using the debugger difficult. I have to turn it off when running a test with the debugger which can change how the test behaves. |
You can try running with parallel => 1, whuch will still fork, but only one As for the chdir, that should be a fennec feature, not a test::workflow
|
I've been using FENNEC_PARALLEL=0 and parallel => 0 with perl -d. Make sure you have Fennec 2.014+ if you want to use the env var. On Tue, Apr 8, 2014 at 6:06 PM, Chad Granum notifications@github.comwrote:
|
I experimentally confirmed that
tests
blocks will return you to the original cwd the test was started in. This is a very useful feature, but I couldn't find it documented in either Fennec or Test::WorkFlow.I'm hesitant to just document it as it appears to be a side effect of forking, and setting
FENNEC_PARALLEL=0
breaks it. I use that when I want to debug tests.Here's a small test to demonstrate the feature.
The text was updated successfully, but these errors were encountered: