Standardize commandline options for test harness
Bug #1225542 reported by
Charlie Poole
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| NUnit Framework |
Fix Released
|
High
|
Charlie Poole | ||
Bug Description
The test harness used to run framework tests has some options which do the same thing as nunit-console options, but which are expressed differently. Where possible, we should use the same options to do the same thing so devs don't have to worry about which runner they are using.
The options processing should be converted to mono-options at the same time.
Related branches
| Changed in nunit-3.0: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Charlie Poole (charlie.poole) |
| milestone: | none → 2.9.6 |
Revision history for this message
| Charlie Poole (charlie.poole) wrote | #1 |
| Changed in nunit-3.0: | |
| status: | Triaged → Fix Committed |
| Changed in nunit-3.0: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Adusted option naming, converted to use mono-options, renamed direct-runner as test-harness and implemented a number of missing commandline features present in nunit-console.