Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


MS Test Runner is not running from correct directory

We have a dotnet project where the Unit Tests run fine locally (dotnet framework, NOT dotnet core). Part of the setup for the tests uses a settings.json file in the test application, which is set to "always copy to the output".

On Bamboo, the tests fail and the reason is that instead of running from TestsProject/bin/debug/Tests.dll, which is specified in the MS Test Runner task, it is running from an "Out" directory in a build folder under the job (in our case it is SL-ENCC123-JOB1\Bamboo_CAROL 2018-05-22 10_21_36\Out), which does NOT have the config file in it, although it does have the rest of the project dlls including the test ones.

1) Why are the tests running from a different directory, that is not obvious

2) Why doesn't it copy the config file to Out even though it is set to always copy

3) What is the correct way to handle this?


1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 30, 2018

Hi Luke,

The Bamboo specialist helping with your question would like to use the direct messaging and file sharing provided by our support portal. I created a support request in your name; you should see a notification email from the portal shortly.

When the issue is resolved we can circle back and let the Community know.



We have this exact same issue.  Are we able to get some insight as to how to fix this?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events