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

NUnit3Settings: Params and multiple results #1665

Closed
Roemer opened this issue Jun 28, 2017 · 1 comment · Fixed by #1666
Closed

NUnit3Settings: Params and multiple results #1665

Roemer opened this issue Jun 28, 2017 · 1 comment · Fixed by #1666

Comments

@Roemer
Copy link
Contributor

Roemer commented Jun 28, 2017

There are some important things missing from the NUnit3Settings class:

Params

It is possible to pass parameters to the tests (which can be read with TestContext.Parameters[].
An example would be:
--params=uia=2
So it's one or more key-value pairs.
It would be great to have that in the NUnit3Settings as well.

Multiple results

In some cases, I need to be able to have multiple result formats.
For example when using Jenkins: Jenkins only understands the v2 format but the v3 format has more information. So I need to have the v2 for Jenkins and v3 in the artefacts.
NUnit-Console allows to receive multiple --result so the current property should be extended to be a list of a new class like NUnit3Result which has a Format, Transform and Name property which would replace the current result properties from NUnit3Settings

@Roemer
Copy link
Contributor Author

Roemer commented Jun 28, 2017

I might make the changes myself and create a PR.
This would lead to breaking changes as some properties would be changed. Is this in general ok or should we create new properties and mark the old ones obsolete?

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

Successfully merging a pull request may close this issue.

2 participants