Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,367
Community Members
 
Community Events
176
Community Groups

NUnit Commandline options issues

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

0 votes
Answer accepted

Found the solution you have to set the parameter like this

"--testparam=Foo=Foo Bar"

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events