Shape the future of Merative!
We invite you to shape the future of Merative, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the Merative team to refine your idea
Help Merative prioritize your ideas and requests
The Merative team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at Merative works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at Merative, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Merative External Privacy Statement: https://www.merative.com/privacy
Hi Garry,
We acknowledge that this enhancement request has been accepted for consideration with the following considerations:
1. We will not be opening the RMIAuthentication class for customers to access directly in their unit test scenarios.
2. What we would propose to do here would be to expose this ability through a wrapper test class. This will ensure we only expose what is needed for this type of functionality and if delivered via a "test infrastructure" mechanism, it will be clear to all that this is not something that cannot be used for any other means other than testing.
It may not be delivered within the release currently under development however the theme is aligned with our current multi-year strategy and will be considered for a future release.
IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting.
IBM will update this request in the future.
Thank you for your interest in the Cúram product.
Shane McFadden, Cúram SPM Product Management team
A number of our junits rely on the current user being part of the org structure, with a valid position, supervisor etc. Hence the RMIAuthentication class has been used to achieve this, calling the login(username,password) method for all of our tests by placing it in junit setup.
Alternative would have been to add 'unauthenticated' user to the org structure which wouldn't be right.
ALso you mention CuramServerTestJUnit4 - where can this be found please?
Hi Garry,
In order to evaluate your request, we require that you provide more details on what the customer is trying to do here before proceeding to comment on the class in question.
- What is the use case that the unit test is being written for?
- What is the need for setting the user and what function within the RMIAuthentication class is being proposed to use for that purpose?
- Have you ascertained that the functions contained within the test framework class (EJBServer\components\core\tests\curam\test\junit4\CuramServerTestJUnit4) would not satisfy these requirements?
Thank you,
Shane McFadden, Cúram SPM Product Management team
Hi Garry,
Thank you for your enhancement request.
We require some further analysis to determine whether or not this enhancement can be considered in a future release.
I will provide another response when our investigation is complete.
Thank you,
Shane McFadden, Cúram SPM Product Management team