Missing basepath and privatebinpath arguments in nunit-console
Bug #1029941 reported by
Patrik Hartlén
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NUnit V2 |
Fix Released
|
Wishlist
|
Simone Busoli |
Bug Description
I'm using the basepath and privatebinpath option when running unit tests programmatic on assembly level and the nunit-console application are missing these arguments. See attached patch files (zip) for suggested implementation.
thanks
Patrik
Related branches
lp:~simone.busoli/nunitv2/nunitv2
- Charlie Poole: Approve
-
Diff: 54 lines (+20/-4)2 files modifiedsrc/ConsoleRunner/nunit-console/ConsoleOptions.cs (+7/-1)
src/ConsoleRunner/nunit-console/ConsoleUi.cs (+13/-3)
tags: | added: console feature |
Changed in nunitv2: | |
milestone: | none → 2.6.2 |
Changed in nunitv2: | |
assignee: | nobody → Simone Busoli (simone.busoli) |
Changed in nunitv2: | |
status: | Triaged → In Progress |
Changed in nunitv2: | |
status: | In Progress → Fix Committed |
Changed in nunitv2: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm doubtful about this feature, although your patch appears to work cleanly. In general, we place settings that are required to run a set of tests in the NUnit project file, while the command line is used for settings that may change from run to run. The basepath and privatebinpath are in the first category and so are handled in the project file. Have you tried that approach? Here's a simple example for the case of a single assembly:
<NUnitProject> "your/applicati on/base" /> "one/path; another/ path"> test/assembly" />
<Settings appbase=
<Config name="Default" binpath=
<assembly path="your/
</Config>
</NUnitProject>
The private binpath is relative to the basepath. All other paths are relative to the location of the .nunit file itself. The basepath defaults to the location of the .nunit file. You can create the file in any text editor, from the NUnit gui or by running the nunit-editor executable.
I'm not rejecting your patch at this time, in case you have reasons why the usual approach won't work for you. However, I don't want to add new options to the command line without good reason.