Mixing
NUnit running classes in parallel
Iam a little bit confused about the Parallel attribute of nunit:
Say i have 3 Classes each filled with some tests:
ClassA
- Test1
- Test2
- Test3
ClassB
- Test1
ClassC
- Test1
- Test2
I would like to run Every Test in ClassA and ClassB in parallel (i dont care about order )
I also would like to run ClassC while ClassA and ClassB are running, but in this class i want to keep the order in which i specified the tests
So my question is how should i set the attributes to get a behaviour like this?
I checked the docu https://github.com/nunit/docs/wiki/Framework-Parallel-Test-Execution but iam still confused
nunit nunit-3.0
asked Nov 20 '18 at 12:26
LoadingLoading
1889
add a comment |
Iam a little bit confused about the Parallel attribute of nunit:
Say i have 3 Classes each filled with some tests:
ClassA
- Test1
- Test2
- Test3
ClassB
- Test1
ClassC
- Test1
- Test2
I would like to run Every Test in ClassA and ClassB in parallel (i dont care about order )
I also would like to run ClassC while ClassA and ClassB are running, but in this class i want to keep the order in which i specified the tests
So my question is how should i set the attributes to get a behaviour like this?
I checked the docu https://github.com/nunit/docs/wiki/Framework-Parallel-Test-Execution but iam still confused
nunit nunit-3.0
asked Nov 20 '18 at 12:26
LoadingLoading
1889
add a comment |
Iam a little bit confused about the Parallel attribute of nunit:
Say i have 3 Classes each filled with some tests:
ClassA
- Test1
- Test2
- Test3
ClassB
- Test1
ClassC
- Test1
- Test2
I would like to run Every Test in ClassA and ClassB in parallel (i dont care about order )
I also would like to run ClassC while ClassA and ClassB are running, but in this class i want to keep the order in which i specified the tests
So my question is how should i set the attributes to get a behaviour like this?
I checked the docu https://github.com/nunit/docs/wiki/Framework-Parallel-Test-Execution but iam still confused
nunit nunit-3.0
asked Nov 20 '18 at 12:26
LoadingLoading
1889
Iam a little bit confused about the Parallel attribute of nunit:
Say i have 3 Classes each filled with some tests:
ClassA
- Test1
- Test2
- Test3
ClassB
- Test1
ClassC
- Test1
- Test2
I would like to run Every Test in ClassA and ClassB in parallel (i dont care about order )
I also would like to run ClassC while ClassA and ClassB are running, but in this class i want to keep the order in which i specified the tests
So my question is how should i set the attributes to get a behaviour like this?
I checked the docu https://github.com/nunit/docs/wiki/Framework-Parallel-Test-Execution but iam still confused
nunit nunit-3.0
nunit nunit-3.0
asked Nov 20 '18 at 12:26
LoadingLoading
1889
asked Nov 20 '18 at 12:26
LoadingLoading
1889
asked Nov 20 '18 at 12:26
LoadingLoading
1889
asked Nov 20 '18 at 12:26
LoadingLoading
1889
asked Nov 20 '18 at 12:26
LoadingLoading
1889
1889
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Starting simple...
If you do nothing with
ParallelizableAttributethen nothing runs in parallel. :-)If you add
Parallelizableto each fixture, then the three fixtures will run in parallel, but the individual tests will not. That is, up to three things can be running at one time, one from each class.If you add
[Parallelizable(ParallelScope.Fixtures)]at the assembly level, the effect is the same as (2). You should only do this if almost all of your fixtures will successfully run in parallel, in which case you would mark those that can't as[NonParallelizable]. My experience in helping people is that too many people do this without realizing that their tests may not always run correctly in parallel when not written to do so. Starting out, it's safest to default to non-parallel and only add it when it works for you.Starting with (2), change the attribute on A and B to
[Parallelizable(ParallelScope.All)]or
[Parallelizable(ParallelScope.Self + ParallelScope.Children). I like the longer form because it's much clearer to readers as to what it does. This will have exactly the effect that you want.
One more note: you should probably make sure that any fixture in which you specify the order of tests does not run in parallel. NUnit let's you specify both parallel and order without error. In that case, it simply starts the tests in the order you give, but that may not be what you intended.
4.
answered Nov 20 '18 at 18:17
CharlieCharlie
6,72911518
add a comment |
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%2f53392977%2fnunit-running-classes-in-parallel%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Starting simple...
If you do nothing with
ParallelizableAttributethen nothing runs in parallel. :-)If you add
Parallelizableto each fixture, then the three fixtures will run in parallel, but the individual tests will not. That is, up to three things can be running at one time, one from each class.If you add
[Parallelizable(ParallelScope.Fixtures)]at the assembly level, the effect is the same as (2). You should only do this if almost all of your fixtures will successfully run in parallel, in which case you would mark those that can't as[NonParallelizable]. My experience in helping people is that too many people do this without realizing that their tests may not always run correctly in parallel when not written to do so. Starting out, it's safest to default to non-parallel and only add it when it works for you.Starting with (2), change the attribute on A and B to
[Parallelizable(ParallelScope.All)]or
[Parallelizable(ParallelScope.Self + ParallelScope.Children). I like the longer form because it's much clearer to readers as to what it does. This will have exactly the effect that you want.
One more note: you should probably make sure that any fixture in which you specify the order of tests does not run in parallel. NUnit let's you specify both parallel and order without error. In that case, it simply starts the tests in the order you give, but that may not be what you intended.
4.
answered Nov 20 '18 at 18:17
CharlieCharlie
6,72911518
add a comment |
Starting simple...
If you do nothing with
ParallelizableAttributethen nothing runs in parallel. :-)If you add
Parallelizableto each fixture, then the three fixtures will run in parallel, but the individual tests will not. That is, up to three things can be running at one time, one from each class.If you add
[Parallelizable(ParallelScope.Fixtures)]at the assembly level, the effect is the same as (2). You should only do this if almost all of your fixtures will successfully run in parallel, in which case you would mark those that can't as[NonParallelizable]. My experience in helping people is that too many people do this without realizing that their tests may not always run correctly in parallel when not written to do so. Starting out, it's safest to default to non-parallel and only add it when it works for you.Starting with (2), change the attribute on A and B to
[Parallelizable(ParallelScope.All)]or
[Parallelizable(ParallelScope.Self + ParallelScope.Children). I like the longer form because it's much clearer to readers as to what it does. This will have exactly the effect that you want.
One more note: you should probably make sure that any fixture in which you specify the order of tests does not run in parallel. NUnit let's you specify both parallel and order without error. In that case, it simply starts the tests in the order you give, but that may not be what you intended.
4.
answered Nov 20 '18 at 18:17
CharlieCharlie
6,72911518
add a comment |
Starting simple...
If you do nothing with
ParallelizableAttributethen nothing runs in parallel. :-)If you add
Parallelizableto each fixture, then the three fixtures will run in parallel, but the individual tests will not. That is, up to three things can be running at one time, one from each class.If you add
[Parallelizable(ParallelScope.Fixtures)]at the assembly level, the effect is the same as (2). You should only do this if almost all of your fixtures will successfully run in parallel, in which case you would mark those that can't as[NonParallelizable]. My experience in helping people is that too many people do this without realizing that their tests may not always run correctly in parallel when not written to do so. Starting out, it's safest to default to non-parallel and only add it when it works for you.Starting with (2), change the attribute on A and B to
[Parallelizable(ParallelScope.All)]or
[Parallelizable(ParallelScope.Self + ParallelScope.Children). I like the longer form because it's much clearer to readers as to what it does. This will have exactly the effect that you want.
One more note: you should probably make sure that any fixture in which you specify the order of tests does not run in parallel. NUnit let's you specify both parallel and order without error. In that case, it simply starts the tests in the order you give, but that may not be what you intended.
4.
answered Nov 20 '18 at 18:17
CharlieCharlie
6,72911518
Starting simple...
If you do nothing with
ParallelizableAttributethen nothing runs in parallel. :-)If you add
Parallelizableto each fixture, then the three fixtures will run in parallel, but the individual tests will not. That is, up to three things can be running at one time, one from each class.If you add
[Parallelizable(ParallelScope.Fixtures)]at the assembly level, the effect is the same as (2). You should only do this if almost all of your fixtures will successfully run in parallel, in which case you would mark those that can't as[NonParallelizable]. My experience in helping people is that too many people do this without realizing that their tests may not always run correctly in parallel when not written to do so. Starting out, it's safest to default to non-parallel and only add it when it works for you.Starting with (2), change the attribute on A and B to
[Parallelizable(ParallelScope.All)]or
[Parallelizable(ParallelScope.Self + ParallelScope.Children). I like the longer form because it's much clearer to readers as to what it does. This will have exactly the effect that you want.
One more note: you should probably make sure that any fixture in which you specify the order of tests does not run in parallel. NUnit let's you specify both parallel and order without error. In that case, it simply starts the tests in the order you give, but that may not be what you intended.
4.
answered Nov 20 '18 at 18:17
CharlieCharlie
6,72911518
answered Nov 20 '18 at 18:17
CharlieCharlie
6,72911518
answered Nov 20 '18 at 18:17
CharlieCharlie
6,72911518
answered Nov 20 '18 at 18:17
CharlieCharlie
6,72911518
6,72911518
add a comment |
add a comment |
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%2f53392977%2fnunit-running-classes-in-parallel%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
