Running NUnit tests with nunit3-console.exe on build machine fails - but they run fine locally
When I try to run the tests from command line on the build machine with
nunit3-console.exe TestProject.dll
I get the following error:
No suitable tests found in TestProject.dll
Either assembly contains no tests or proper test driver has not been found.
But I can run the tests locally, both from Visual Studio and from the command line with, so I tests are there. But somehow they just won't run on the build machine.
How can I go about fixing this?
nunit nunit-console
asked Nov 15 '18 at 10:29
Ola EldøyOla Eldøy
3,33353766
add a comment |
When I try to run the tests from command line on the build machine with
nunit3-console.exe TestProject.dll
I get the following error:
No suitable tests found in TestProject.dll
Either assembly contains no tests or proper test driver has not been found.
But I can run the tests locally, both from Visual Studio and from the command line with, so I tests are there. But somehow they just won't run on the build machine.
How can I go about fixing this?
nunit nunit-console
asked Nov 15 '18 at 10:29
Ola EldøyOla Eldøy
3,33353766
Verify that you are running the same version of nunit3-console and using the same version of the nunit framework in both environments.
– Charlie
Nov 15 '18 at 10:56
The framework binaries were missing from the bin folder. The source of the problem was actually to do with the checkout from source control.
– Ola Eldøy
Nov 15 '18 at 12:14
add a comment |
When I try to run the tests from command line on the build machine with
nunit3-console.exe TestProject.dll
I get the following error:
No suitable tests found in TestProject.dll
Either assembly contains no tests or proper test driver has not been found.
But I can run the tests locally, both from Visual Studio and from the command line with, so I tests are there. But somehow they just won't run on the build machine.
How can I go about fixing this?
nunit nunit-console
asked Nov 15 '18 at 10:29
Ola EldøyOla Eldøy
3,33353766
When I try to run the tests from command line on the build machine with
nunit3-console.exe TestProject.dll
I get the following error:
No suitable tests found in TestProject.dll
Either assembly contains no tests or proper test driver has not been found.
But I can run the tests locally, both from Visual Studio and from the command line with, so I tests are there. But somehow they just won't run on the build machine.
How can I go about fixing this?
nunit nunit-console
nunit nunit-console
asked Nov 15 '18 at 10:29
Ola EldøyOla Eldøy
3,33353766
asked Nov 15 '18 at 10:29
Ola EldøyOla Eldøy
3,33353766
asked Nov 15 '18 at 10:29
Ola EldøyOla Eldøy
3,33353766
asked Nov 15 '18 at 10:29
Ola EldøyOla Eldøy
3,33353766
asked Nov 15 '18 at 10:29
Ola EldøyOla Eldøy
3,33353766
3,33353766
Verify that you are running the same version of nunit3-console and using the same version of the nunit framework in both environments.
– Charlie
Nov 15 '18 at 10:56
The framework binaries were missing from the bin folder. The source of the problem was actually to do with the checkout from source control.
– Ola Eldøy
Nov 15 '18 at 12:14
add a comment |
Verify that you are running the same version of nunit3-console and using the same version of the nunit framework in both environments.
– Charlie
Nov 15 '18 at 10:56
The framework binaries were missing from the bin folder. The source of the problem was actually to do with the checkout from source control.
– Ola Eldøy
Nov 15 '18 at 12:14
Verify that you are running the same version of nunit3-console and using the same version of the nunit framework in both environments.
– Charlie
Nov 15 '18 at 10:56
Verify that you are running the same version of nunit3-console and using the same version of the nunit framework in both environments.
– Charlie
Nov 15 '18 at 10:56
The framework binaries were missing from the bin folder. The source of the problem was actually to do with the checkout from source control.
– Ola Eldøy
Nov 15 '18 at 12:14
The framework binaries were missing from the bin folder. The source of the problem was actually to do with the checkout from source control.
– Ola Eldøy
Nov 15 '18 at 12:14
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317363%2frunning-nunit-tests-with-nunit3-console-exe-on-build-machine-fails-but-they-ru%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317363%2frunning-nunit-tests-with-nunit3-console-exe-on-build-machine-fails-but-they-ru%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Verify that you are running the same version of nunit3-console and using the same version of the nunit framework in both environments.
– Charlie
Nov 15 '18 at 10:56
The framework binaries were missing from the bin folder. The source of the problem was actually to do with the checkout from source control.
– Ola Eldøy
Nov 15 '18 at 12:14