Is there a change in Unit testing framework from RTC-5.0.2 to EWM-7.0.2
We have extended lot of RTC functionality and developed new features in our custom environment. We had written Test suite for Junit Plugin testing in RTC-5.0.2 and now post upgrading to EWM-7.0.2 SR1 when we try to run test cases we are seeing lot of errors related to eclipse plugins. Is there a major change in the APIs. While validating plugins we are getting Platform filter errors and Missing constraints errors. Please guide us on debugging this error. Also please share any documentation which help in understanding trying Junit test cases for EWM-7.0.2SR1. Thanks
3 answers
I have been maintaining the EWM Extensions workshop and have used the EWM APIs and the EWM SDK for years. I am not aware of breaking API changes since RTC 2.0. There have been minor API changes I have seen in the past that, if used, broke the code for previous versions, which is to be expected.
My expectation would be that customers that use the APIs and especially the SDK install the EWM Extensions Workshop for the release they wish to upgrade to and load their code into the relevant workspaces. Then they should test their code in that environment. In the past it was easy enough to do and I never experienced any breaking changes as mentioned.
But for 7.0.2 SR1 you want to look at my blog how to get the environment to work. If you do not follow these hints, you are likely not going to able to use the Extensions Workshop. I have published hints and erratas on this blog https://rsjazz.wordpress.com/ every time I found issues with the Extensions Workshop or the APIs. You can search the blog and the posts are also tagged.
But for 7.0.2 SR1 you want to look at my blog how to get the environment to work. If you do not follow these hints, you are likely not going to able to use the Extensions Workshop. I have published hints and erratas on this blog https://rsjazz.wordpress.com/ every time I found issues with the Extensions Workshop or the APIs. You can search the blog and the posts are also tagged.
In addition to the SSL issues mentined in my blog, EWM 7.0.2 SR1 has a breaking change in the SDK, as it removes Log4J1 and adds Log4J2. This removes libraries and requires manual changes, if you implemented logging.
EWM 6.x and 7.x require different Java Versions. 7.0.2 requires Java 8. This could contribute, but should not be an issue if you follow the Extensions Workshop.
If plugins and features are done correctly, as described in the Extensions Workshop, they should automatically pick up newer versions of plugins and features in the target platform/SDK. If there are dependency issues, Eclipse and the compiler should be guides to find out what the issue is. If the environment works and you see errors you need to find out what the reason is. Use Jetty for initial testing. If the stuff compiles and works in general, follow your Unit tests to find out what is going wrong. It is your JUnit testing, I am not aware of any dramatic changes in the unit testing frameworks, except maybe a newer JUnit version compared to the ancient EWM 5.0.x.
I am not aware of documentation for specifics in EWM APIs, besides the Extensions Workshop and the Developer Wiki, see https://jazz.net/wiki/bin/view/Deployment/CLMProductAPILanding for places for specific APIs.
I am not sure if documentation would help, Who reads documentation?
Your question is devoid of any useful information with respect to the issue you see, so you should not expect any detailed help.
If plugins and features are done correctly, as described in the Extensions Workshop, they should automatically pick up newer versions of plugins and features in the target platform/SDK. If there are dependency issues, Eclipse and the compiler should be guides to find out what the issue is. If the environment works and you see errors you need to find out what the reason is. Use Jetty for initial testing. If the stuff compiles and works in general, follow your Unit tests to find out what is going wrong. It is your JUnit testing, I am not aware of any dramatic changes in the unit testing frameworks, except maybe a newer JUnit version compared to the ancient EWM 5.0.x.
I am not aware of documentation for specifics in EWM APIs, besides the Extensions Workshop and the Developer Wiki, see https://jazz.net/wiki/bin/view/Deployment/CLMProductAPILanding for places for specific APIs.
I am not sure if documentation would help, Who reads documentation?
Your question is devoid of any useful information with respect to the issue you see, so you should not expect any detailed help.
Thanks for your response. Actually while building the code and deploying the plugins to server is working. But the main issue I am facing is while running the test suite. I am unable to run the test cases as using Junit plugin Test. I am facing issues while validating the plugins and it is throwing errors related to eclipse jars.
Also I am getting errors related to plugins validation.
Comments
