Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WFLY-4391] : When testing with WildFly Full, the WSTestCase is randomly unstable #7206

Merged
merged 2 commits into from Feb 27, 2015

Conversation

ehsavoie
Copy link
Contributor

It seems that the test relies on WS metrics update which might occurs after the response has been received and processed by the client.
Thus we may get a race.

Jira: https://issues.jboss.org/browse/WFLY-4391

@wildfly-ci
Copy link

Windows Build 1086 is now running using a merge of 5d21060

@wildfly-ci
Copy link

Linux Build 5973 is now running using a merge of 5d21060

@wildfly-ci
Copy link

Linux with security manager Build 952 is now running using a merge of 5d21060

@wildfly-ci
Copy link

Linux with security manager Build 952 outcome was SUCCESS using a merge of 5d21060
Summary: Tests passed: 840, ignored: 319 Build time: 0:06:45

@wildfly-ci
Copy link

Linux Build 5973 outcome was SUCCESS using a merge of 5d21060
Summary: Tests passed: 2928, ignored: 313, muted: 1 Build time: 0:46:45

@wildfly-ci
Copy link

Windows Build 1086 outcome was SUCCESS using a merge of 5d21060
Summary: Tests passed: 2928, ignored: 313, muted: 1 Build time: 0:48:00

@@ -98,16 +107,17 @@ public void testManagementDescription() throws Exception {
operation.get(ModelDescriptionConstants.RECURSIVE).set(true);

final ModelNode result = managementClient.getControllerClient().execute(operation);
Assert.assertEquals(ModelDescriptionConstants.SUCCESS, result.get(ModelDescriptionConstants.OUTCOME).asString());

assertThat(result.get(ModelDescriptionConstants.OUTCOME).asString(), is(ModelDescriptionConstants.SUCCESS));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ehsavoie all these replacements of Assert.assertEquals() with assertThat() seem pointless, and also make it hard to see exactly what has been changed. If we really 'must' do this replacement, please do so as a separate commit.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well it helps has you won't get a null assertion for the assertTrue but a more meaningfull message
As for assertEquals I changed those where we are testing for success on operation result, but I missed the line you are referencing

@wildfly-ci
Copy link

Windows Build 1088 is now running using a merge of be187c3

@wildfly-ci
Copy link

Linux with security manager Build 954 is now running using a merge of be187c3

@wildfly-ci
Copy link

Linux Build 5975 is now running using a merge of be187c3

@wildfly-ci
Copy link

Linux with security manager Build 954 outcome was SUCCESS using a merge of 30653a2
Summary: Tests passed: 840, ignored: 319 Build time: 0:04:57

…mly unstable

It seems that the test relies on WS metrics update which might occurs after the response has been received and processed by the client.
Thus we may get a race.
…mly unstable

Cleaning the test code to have more meaningfull assertion errors.
@wildfly-ci
Copy link

Linux Build 5975 outcome was SUCCESS using a merge of c5b1aa9
Summary: Tests passed: 2928, ignored: 314, muted: 1 Build time: 0:46:44

@wildfly-ci
Copy link

Windows Build 1088 outcome was SUCCESS using a merge of c5b1aa9
Summary: Tests passed: 2928, ignored: 314, muted: 1 Build time: 0:48:08

@wildfly-ci
Copy link

Linux Build 5976 is now running using a merge of c5b1aa9

@wildfly-ci
Copy link

Windows Build 1089 is now running using a merge of c5b1aa9

@wildfly-ci
Copy link

Linux with security manager Build 955 is now running using a merge of c5b1aa9

@wildfly-ci
Copy link

Linux with security manager Build 955 outcome was SUCCESS using a merge of c5b1aa9
Summary: Tests passed: 840, ignored: 319 Build time: 0:04:57

@wildfly-ci
Copy link

Linux Build 5976 outcome was SUCCESS using a merge of c5b1aa9
Summary: Tests passed: 2928, ignored: 314, muted: 1 Build time: 0:47:51

@wildfly-ci
Copy link

Windows Build 1089 outcome was SUCCESS using a merge of c5b1aa9
Summary: Tests passed: 2928, ignored: 314, muted: 1 Build time: 0:48:50

bstansberry added a commit that referenced this pull request Feb 27, 2015
[WFLY-4391] : When testing with WildFly Full, the WSTestCase is randomly unstable
@bstansberry bstansberry merged commit c743145 into wildfly:master Feb 27, 2015
@ehsavoie ehsavoie deleted the WFLY-4391 branch September 25, 2015 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants