Skip to content
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

Allow one to set the Internal Trace location #1388

Closed
WindingWinter opened this issue Feb 21, 2024 · 1 comment
Closed

Allow one to set the Internal Trace location #1388

WindingWinter opened this issue Feb 21, 2024 · 1 comment

Comments

@WindingWinter
Copy link

I use the command line parameter --trace=Verbose, and I found that Internal Trace file will be generated at my current directory.

But is there a flexibility for me to specify where can I put my Internal Trace file? Because when I start from command line prompt, I can start anywhere, including from C drive.

@CharliePoole
Copy link
Collaborator

The console runner stores both log files and the TestResult.xml file in a "working directory." This defaults to your current directory but may be changed by using the --work option on the command-line.

As an historical note, NUnit V2 actually changed the process current directory to be that of the test assembly. We stopped changing current directory in V3, because that's considered bad behavior for an application.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants