Arquillian cube repeats each unit test multiple times
We are using Arquillian cube with JUnit to test containerised SpringBoot microservices. This works fine, but for some reason the test harness is executing each individual test multiple times - 2, 3, sometimes 4 times each. I can see no reason for this or find anything to explain it in the docs, and it's a nuisance rather than a major problem (at the moment).
Here is a cut down test class which I have used to demonstrate the issue:
@RunWith(Arquillian.class)
@RunAsClient
public class MyTests {
@CubeIp(containerName = "test")
private String cubeIp;
@Test
@InSequence(2)
public void test1() {
System.out.println("executing test1");
}
@Test
@InSequence(2)
public void test2() {
System.out.println("executing test2");
}
}
The console output with this example would show repeated debug for each test. The dockerContainers
configuration in arquillian.xml
looks like this:
test:
image: my-image:1.0
await:
strategy: sleeping
sleepTime: 30 s
portBindings: [1080->1080/tcp]
restartPolicy:
name: failure
maximumRetryCount: 1
links:
- other-container:other-container
other-container:
image: other-container:1.0
portBindings: [8080->8080/tcp]
restartPolicy:
name: failure
maximumRetryCount: 1
As can be seen, there is a second container other-container
which mimics the behaviour of an upstream service. Both are started and stopped correctly. I have tried upgrading all relevant Arquillian dependencies to the latest versions, but the problem persists.
Advice on why this is happening, whether it is expected behaviour (and why) or what we might be doing wrong in our config would be appreciated.
java spring-boot docker junit jboss-arquillian
add a comment |
We are using Arquillian cube with JUnit to test containerised SpringBoot microservices. This works fine, but for some reason the test harness is executing each individual test multiple times - 2, 3, sometimes 4 times each. I can see no reason for this or find anything to explain it in the docs, and it's a nuisance rather than a major problem (at the moment).
Here is a cut down test class which I have used to demonstrate the issue:
@RunWith(Arquillian.class)
@RunAsClient
public class MyTests {
@CubeIp(containerName = "test")
private String cubeIp;
@Test
@InSequence(2)
public void test1() {
System.out.println("executing test1");
}
@Test
@InSequence(2)
public void test2() {
System.out.println("executing test2");
}
}
The console output with this example would show repeated debug for each test. The dockerContainers
configuration in arquillian.xml
looks like this:
test:
image: my-image:1.0
await:
strategy: sleeping
sleepTime: 30 s
portBindings: [1080->1080/tcp]
restartPolicy:
name: failure
maximumRetryCount: 1
links:
- other-container:other-container
other-container:
image: other-container:1.0
portBindings: [8080->8080/tcp]
restartPolicy:
name: failure
maximumRetryCount: 1
As can be seen, there is a second container other-container
which mimics the behaviour of an upstream service. Both are started and stopped correctly. I have tried upgrading all relevant Arquillian dependencies to the latest versions, but the problem persists.
Advice on why this is happening, whether it is expected behaviour (and why) or what we might be doing wrong in our config would be appreciated.
java spring-boot docker junit jboss-arquillian
Exploring with Arquillian team via this issue: github.com/arquillian/arquillian-cube/issues/1105
– Tom Bunting
Dec 4 '18 at 16:27
add a comment |
We are using Arquillian cube with JUnit to test containerised SpringBoot microservices. This works fine, but for some reason the test harness is executing each individual test multiple times - 2, 3, sometimes 4 times each. I can see no reason for this or find anything to explain it in the docs, and it's a nuisance rather than a major problem (at the moment).
Here is a cut down test class which I have used to demonstrate the issue:
@RunWith(Arquillian.class)
@RunAsClient
public class MyTests {
@CubeIp(containerName = "test")
private String cubeIp;
@Test
@InSequence(2)
public void test1() {
System.out.println("executing test1");
}
@Test
@InSequence(2)
public void test2() {
System.out.println("executing test2");
}
}
The console output with this example would show repeated debug for each test. The dockerContainers
configuration in arquillian.xml
looks like this:
test:
image: my-image:1.0
await:
strategy: sleeping
sleepTime: 30 s
portBindings: [1080->1080/tcp]
restartPolicy:
name: failure
maximumRetryCount: 1
links:
- other-container:other-container
other-container:
image: other-container:1.0
portBindings: [8080->8080/tcp]
restartPolicy:
name: failure
maximumRetryCount: 1
As can be seen, there is a second container other-container
which mimics the behaviour of an upstream service. Both are started and stopped correctly. I have tried upgrading all relevant Arquillian dependencies to the latest versions, but the problem persists.
Advice on why this is happening, whether it is expected behaviour (and why) or what we might be doing wrong in our config would be appreciated.
java spring-boot docker junit jboss-arquillian
We are using Arquillian cube with JUnit to test containerised SpringBoot microservices. This works fine, but for some reason the test harness is executing each individual test multiple times - 2, 3, sometimes 4 times each. I can see no reason for this or find anything to explain it in the docs, and it's a nuisance rather than a major problem (at the moment).
Here is a cut down test class which I have used to demonstrate the issue:
@RunWith(Arquillian.class)
@RunAsClient
public class MyTests {
@CubeIp(containerName = "test")
private String cubeIp;
@Test
@InSequence(2)
public void test1() {
System.out.println("executing test1");
}
@Test
@InSequence(2)
public void test2() {
System.out.println("executing test2");
}
}
The console output with this example would show repeated debug for each test. The dockerContainers
configuration in arquillian.xml
looks like this:
test:
image: my-image:1.0
await:
strategy: sleeping
sleepTime: 30 s
portBindings: [1080->1080/tcp]
restartPolicy:
name: failure
maximumRetryCount: 1
links:
- other-container:other-container
other-container:
image: other-container:1.0
portBindings: [8080->8080/tcp]
restartPolicy:
name: failure
maximumRetryCount: 1
As can be seen, there is a second container other-container
which mimics the behaviour of an upstream service. Both are started and stopped correctly. I have tried upgrading all relevant Arquillian dependencies to the latest versions, but the problem persists.
Advice on why this is happening, whether it is expected behaviour (and why) or what we might be doing wrong in our config would be appreciated.
java spring-boot docker junit jboss-arquillian
java spring-boot docker junit jboss-arquillian
asked Nov 21 '18 at 22:45
Tom BuntingTom Bunting
1,079717
1,079717
Exploring with Arquillian team via this issue: github.com/arquillian/arquillian-cube/issues/1105
– Tom Bunting
Dec 4 '18 at 16:27
add a comment |
Exploring with Arquillian team via this issue: github.com/arquillian/arquillian-cube/issues/1105
– Tom Bunting
Dec 4 '18 at 16:27
Exploring with Arquillian team via this issue: github.com/arquillian/arquillian-cube/issues/1105
– Tom Bunting
Dec 4 '18 at 16:27
Exploring with Arquillian team via this issue: github.com/arquillian/arquillian-cube/issues/1105
– Tom Bunting
Dec 4 '18 at 16:27
add a comment |
1 Answer
1
active
oldest
votes
Removal of <artifactId>arquillian-protocol-servlet</artifactId>
from our POM, which had been inadvertently included, solved this issue.
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%2f53421481%2farquillian-cube-repeats-each-unit-test-multiple-times%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
Removal of <artifactId>arquillian-protocol-servlet</artifactId>
from our POM, which had been inadvertently included, solved this issue.
add a comment |
Removal of <artifactId>arquillian-protocol-servlet</artifactId>
from our POM, which had been inadvertently included, solved this issue.
add a comment |
Removal of <artifactId>arquillian-protocol-servlet</artifactId>
from our POM, which had been inadvertently included, solved this issue.
Removal of <artifactId>arquillian-protocol-servlet</artifactId>
from our POM, which had been inadvertently included, solved this issue.
answered Feb 12 at 17:55
Tom BuntingTom Bunting
1,079717
1,079717
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%2f53421481%2farquillian-cube-repeats-each-unit-test-multiple-times%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
Exploring with Arquillian team via this issue: github.com/arquillian/arquillian-cube/issues/1105
– Tom Bunting
Dec 4 '18 at 16:27