The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

NUnit Commandline options issues

Mattias
November 3, 2020

I am trying to set up a NUnit 3 task and have issues passing the required commandline options to the test. The test expects parameters that include spaces (e.g. --testparam=Foo="Foo Bar"), but it gets parsed to

TestParametersDictionary:
Foo -> Foo

and t hen tries to use the "Bar" as a test input instead. For some reason the quotes get ignored. I already tried escaping the quotes, but then I get

TestParametersDictionary:
Foo -> "Foo Bar"

The expected results would be

TestParametersDictionary:
Foo -> Foo Bar

without any quotes. When running NUnit with the above --testparam=Foo="Foo Bar" everything works fine. It is just when it is done from the Bamboo task that things break.

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Mattias
November 18, 2020

Found the solution you have to set the parameter like this

"--testparam=Foo=Foo Bar"
TAGS
AUG Leaders

Atlassian Community Events