Standardize commandline options for nunitlite runner
Bug #1225544 reported by
Charlie Poole
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| NUnit Framework |
Triaged
|
High
|
Charlie Poole | ||
Bug Description
[Issue now tracked at https:/
The NUnitLite integrated runner supports some of the same features as the full nunit-console but uses different options to access them. To the extent possible, where the features are common, we should use the same options in both programs.
NUnitLite commandline option processing should be converted to use Mono.Options at the same time.
| 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: | |
| milestone: | 2.9.6 → none |
| description: | updated |
| tags: | added: github |
To post a comment you must log in.
Made some minor changes. However, it turns out that mono.options won't compile in the compact framework, making it unsuitable for NUnitLite. Postponing this for a later release when we can give more thought to a common approach to commandline interpretation across all nunit projects.