Can anyone answer to my above questions?
Thanks in advance
The different editions are just different configurations of the Jtest license features. They are used to select which Jtest features are in use when using a Parasoft License Server. They are especially useful when different licenses for the same product are installed on the license server and you want to specify which license you want to use. The desktop edition is typically used when you only need to use Jtest from the IDE. The automation edition is used when you need to use Jtest from CLI/maven/gradle. The custom edition is used when you need to specify a custom set of features that need to be enabled that is different than the features configured by the desktop or automation editions.
I have started using 10.4.1 and the new features that have been added is really good and thanks for that.
I face some weird issues while using jtest. Whenever I am generating any new junit method or using any recommendations and after that running that test methods with as jtest it is not reflecting changes.
But if i run that same with eclipse default as junit it is reflecting. And after than when I run same as jtest I can see new recommendations coverage all looks fine.
So is there any issues with my configuration or tools or something I am missing here?
Thanks for the feedback on 10.4.1 - I'm glad the features are helpful for you!
Regarding the issue that you are facing, have you confirmed that your new or updated test class is being recompiled before you run tests? If the test class did not get compiled after changes that would explain why the changes were not reflected.
If that is not the issue, I would recommend that you contact Parasoft support with your specific issue. We have not had any other users report this kind of issue, so I suspect there might be something in your environment that is causing the problem but it's hard to tell without having someone look at it with you.
Thanks for clarification. I have tried to check the point that you have mentioned :
"If the test class did not get compiled after changes that would explain why the changes were not reflected."
but I could not get any clue on how to verify that. All IDE configuration looks ok to me.
Is there any changes I should to so that when it will run as Jtest , code will get compiled 1st and then run as junit?
If you are using Eclipse, go to the Project menu and make sure that "Build Automatically" is checked. If you are using IntelliJ, Jtest will recompile the project for you automatically.
Hope you are doing well. I have observed something weird while using Jtest in spring.
Jtest is not giving any kind of recommendation for Template kind of object like RestTemplate or JDBCtemplate. Its is injecting that object in test class with @mockbean but after I run the junit there is no recommendation to mock the method invocation by this object . Is this a known issue and already addressed or something I am missing here?
Hi @subratdash8 ,
This is a known limitation of the mocking functionality in Jtest. It happens only for mocked types which are defined in an external library such as Spring. For types which are defined in your source code, recommendations should work as expected.
For more details or questions, feel free to reach out to Parasoft support.
Thanks for update. So will that be addressed in any of jtest release?
Because there might be more case where developers need to mock this kind of external libraries call.
Regarding parasoft support, can you please tell how to contact? It should be through my company or directly I can reach to them
Yes, this issue will be addressed in the next Jtest release.
To contact Parasoft Support, log in to the Parasoft customer portal on the parasoft.com website. If you don't already have an account there you can register and someone on the support team will verify that your company is a customer that is entitled to support. Once verified, you will be able to submit support cases directly through the customer portal.