Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jaxrs-dev] [External] : Re: Do you plan to move your TCK tests out of the Platform TCK project for Jakarta EE 10+?
Thanks James.  I tried the Alpha9 with no luck, but I can try the Alpha10.

Although the conversation has gone stale in the last few days, we've been discussing this issue in slack at:
https://eclipsefoundationhq.slack.com/archives/C0131MLD538/p1624542758005000

Thanks again,

Andy

On Wed, Jul 7, 2021 at 10:42 AM James Perkins <jperkins@xxxxxxxxxx> wrote:
Arquillian does have an Alpha version which supports JUnit 5 and the Jakarta EE 9 package rename [1]. The adapters would need to support it however as well.


On Wed, Jul 7, 2021 at 6:52 AM Andy McCright <j.andrew.mccright@xxxxxxxxx> wrote:
Hi Alwin,

I have not had any luck with getting JUnit5 and Arquillian to work correctly. This combination is able to recognize the tests, but it always marks them as passed without actually running the tests.

I've started work on using TestNG with Arquillian (similar to the MicroProfile TCK test framework). I'm still running into issues, but that combination runs the tests at least.  Assuming that this combination works, we'll need to decide whether we should use a hybrid (JUnit 5 for some tests, TestNG for others) or swap the existing tests to TestNG.

Once I get a little further in my sandbox, I'll share my changes.  Thanks for reaching out!

Andy

On Wed, Jul 7, 2021 at 8:45 AM Alwin Joseph <alwin.joseph@xxxxxxxxxx> wrote:

Hi Andy,

 

We have done a POC to move few of the jaxrs standalone TCK tests from jakartaee-tck repo to jaxrs-api , on top of the new JUnit5-based TCK created by Markus. The changes are present in [1] if it helps. This change currently uses Junit5 to run 15 api tests in folder jakartaee-tck/src/com/sun/ts/tests/ jaxrs/api/rs/core/responsebuilder .

 

But this does not cover the majority server side tests which would need Arquillian approach. We will also look into the same to use Arquillian on a set of server tests. If you had any progress on that, it would help to share the same.

 

[1] https://github.com/alwin-joseph/jaxrs-api/tree/migrate-responsebuilder-tests

 

Thanks & Regards,
Alwin Joseph

From: jaxrs-dev <jaxrs-dev-bounces@xxxxxxxxxxx> on behalf of Andy McCright <j.andrew.mccright@xxxxxxxxx>
Reply to: jaxrs developer discussions <jaxrs-dev@xxxxxxxxxxx>
Date: Wednesday, 23 June 2021 at 4:30 AM
To: jaxrs developer discussions <jaxrs-dev@xxxxxxxxxxx>
Subject: [External] : Re: [jaxrs-dev] Do you plan to move your TCK tests out of the Platform TCK project for Jakarta EE 10+?

 

Hi Scott,

 

Markus has already started creation of some JUnit5-based TCK tests for the standalone (Java SE) APIs.  

I've been looking at a JUnit5/Arquillian approach for the server side tests, but running into problems with the integration - to be fair, the JUnit5/Arquillian modules are listed as alpha release, so I might be running into alpha-related issues - or I might just be running into user-error territory... in any case, I think it's fair to say that we are planning to have a standalone TCK for EE10.  Hopefully, we'll actually get there in time! :-)

 

Thanks,

 

Andy 

 

On Tue, Jun 22, 2021 at 2:36 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:

[1][2] is a proposal for how to produce Standalone TCKs by extracting TCK tests from the Platform TCK.  The process for extracting Standalone TCK tests is described via the GUIDELINE FOR EXTRACTING TCK section [3].

Do you plan to move your TCK tests out of the Platform TCK project and into your Specification project?  If yes, you will publish your Standalone TCK artifacts to Maven so that the Platform TCK can consume your tests.  Some Standalone Specification TCKs will also be consumed by the Core Profile TCK (and possibly other EE profiles).

>From the [1] feedback received so far, both TestNG + Junit5 are popular test frameworks.  Maven is the likely choice to switch to using in the EE Platform TCKs.

The Platform TCK community needs to take a deep look at the Platform TCK internals and consider what the Jakarta EE 10+ Platform TCK architecture will look like.  But I think first, we should do some incremental hacking to bring in some Maven based testing as suggested by jakartaee-tck/issues/51 [4].

Scott

[1] https://docs.google.com/document/d/1yDXTUUULUrFrUi1DV_9OcBKIiZLVxrZkA38MMvYdP-U/edit#
[2] https://github.com/eclipse-ee4j/jakartaee-platform/issues/333
[3] https://docs.google.com/document/d/1yDXTUUULUrFrUi1DV_9OcBKIiZLVxrZkA38MMvYdP-U/edit#heading=h.gt76s6wqkrva
[4] https://github.com/eclipse-ee4j/jakartaee-tck/issues/51

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

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


--
James R. Perkins
JBoss by Red Hat
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jaxrs-dev

Back to the top