Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cu-dev] [jakartaee-tck-dev] Removing Concurrency TCK tests from platform repository
Hello All,

Thanks for all the feedback.
Since the last update to this topic both of the outstanding issues brought up on removing the Concurrency TCK from the platform-tck have been contradicted.

A mechanism for repeating tests to run within an EJB and JSP class (currently only using servlets). Related Issue: https://github.com/eclipse-ee4j/concurrency-api/issues/178
In this case, I was brief in my description of what has been moved from the platform TCK to the standalone TCK.
What I meant to say was that we did not port over the "vehicle" test infrastructure, since the only tests that used that feature were the API tests which only tested method return values and exception paths which do not depend on where they run to verify.
So for now all the API tests are only running on servlets.
However, we do still have EJB and JSP tests for the code paths where that matters, such as context propagation.

A mechanism for choosing to run tests in a Java SE vs Jakarta EE Environment. Related Issue: https://github.com/eclipse-ee4j/concurrency-api/issues/179
 For this issue, it was pointed out that the Platform Concurrent TCK never ran against Java SE and so we should not be expected to run against Java SE as part of the Standalone Concurrent TCK.

 So the question is now, can we move forward with removing the Concurrency TCK tests from the platform repo? Related PR: https://github.com/eclipse-ee4j/jakartaee-tck/pull/816

Thanks, everyone for your time,
Kyle Jon Aure

On Tue, Feb 22, 2022 at 12:29 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:
Adding Platform mailing list. 

Thanks Kyle for sending this!

Scott

On Thu, Feb 17, 2022 at 3:47 PM Kyle Aure <kylejaure@xxxxxxxxx> wrote:
Good Afternoon,

I recently opened a PR to remove the concurrency TCK tests from the Platform TCK repository

I did this because I helped port the Concurrency TCK tests to be a standalone project as part of the concurrency-api repository.
I have already received some feedback on the removal of the TCK from the platform repository that we need to implement some additional requirements:
1. A mechanism for repeating tests to run within an EJB and JSP class (currently only using servlets). Related Issue: https://github.com/eclipse-ee4j/concurrency-api/issues/178
2. A mechanism for choosing to run tests in a Java SE vs Jakarta EE Environment. Related Issue: https://github.com/eclipse-ee4j/concurrency-api/issues/179

I am working on solutions for both of these issues, but they are unlikely to be implemented until after Jakarta 10.
I was asked to send out this email by Scott Marlow to get some more feedback on removing the TCK from the platform repository, and if there is anything else that still needs to be implemented in our standalone TCK.

Thank you for your time,

KYLE JON AURE WebSphere Development Office: Roch Bldg 50-2 H220 Phone: 507-253-8454 Email: kyle.aure@xxxxxxx

_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev

Back to the top