-
Notifications
You must be signed in to change notification settings - Fork 133
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
[EJBCLIENT-225] Reinstate ignored test cases post EJBCLIENT-216. #273
Conversation
Build 587 outcome was FAILURE using a merge of 423669f Failed tests
|
Looking into this. Unfortunately, when a client can't find a deployment, there isn't a lot of useful information provided as with the old client. We might want to think about addressing this somehow. |
Build 592 outcome was FAILURE using a merge of 386d616 Failed tests
|
Build 595 outcome was FAILURE using a merge of 826e8b5 Failed tests
|
Build 596 outcome was FAILURE using a merge of c92ae2d Failed tests
|
Found the problem here. In my test case, I have a non-clustered test and a clustered test, and they use two different legacy properties files: clustered-jboss-ejb-client.properties and jboss-ejb-client.properties. When I run the test case locally, the clustered test case runs first, the non-clustered test case runs second; when I run remotely, it is the other way around. It seems as though JBossEJBProperties is being initialised statically once and once only for all tests. So, the properties passed to my test cases depend on the test case order. Need a way to reinit the JBossEJBProperties for each test. |
Build 601 outcome was FAILURE using a merge of c92ae2d Failed tests
|
Build 604 outcome was FAILURE using a merge of c92ae2d Failed tests
|
Didn't have a lot of luck in re-initializing the EJBClientContext after it had been statically initialized with the wrong properties file, so opted for running each test in a new JVM (forkMode=always) and setting the JBossEJBProperties ContextManager with the correct default before any tests run. |
The PR un-ignores the two cluster-based test cases which will pass now that EJBCLIENT-216 is merged.