Re: [jakartaee-tck-dev] discussion around jakartaee-tck/issues#51 and Tu

[Scott Marlow <smarlow@xxxxxxxxxx>]

On 4/22/19 5:11 PM, Bill Shannon wrote:
> In some cases a spec will have "conditional requirements" that apply only
> when it is part of a Java EE product; tests for those requirements ought
> to move the the TCK to the spec project.

Anything is possible but I suspect that some spec projects, will prefer 
to only focus on the technologies that are in that spec project.  So, 
those tests might not get the love that they deserve, in new revisions 
of the spec project that are aligned with a new Jakarta EE 
release/version.

It just isn't possible to make everyone happy on this effort to split 
the CTS/TCKs up, in that I think there will be pain somewhere, 
regardless of which options we follow for splitting the CTS/TCKs up.

> Some other tests are for requirements in the platform spec; those tests
> ought to remain with the CTS.

Agreed.

> I don't know how easy it will be to determine which tests fall into the
> above categories.

I have been worried about chicken and egg situations, where tests might 
live in a standalone TCK but require various containers to run the test.

If a spec project is designing a new revision to be part of a new 
Jakarta EE release/version (e.g. Jakarta EE 20), the spec project could 
test with containers from the last released Jakarta EE release/version 
(e.g. Jakarta EE 19, but the spec project TCK tests, won't be able to 
use newer container features being added to Jakarta EE 20 (at least not 
easily, since Jakarta EE 20 container implementations might not be 
available yet).

I'm not arguing for/against here, just trying to discuss some of the 
challenges with splitting the CTS/TCKs into separate projects, so we can 
identify pros/cons with different approaches.

Scott

> Scott Marlow wrote on 4/22/19 7:29 AM:
> > On 4/17/19 2:30 PM, Scott Marlow wrote:
> > > Another question related to [1], is about the moving of tests from the
> > > jakartaee-tck repo [2], to the respective SPEC API projects, so that the said
> > > tests can be maintained as part of the SPEC API project specific (standalone)
> > > TCK.  Should the tests that require a Jakarta EE implementation to run, also
> > > be moved to the respective SPEC API project?   Or does it make more sense to
> > > leave the Jakarta EE tests in the jakartaee-tck [2] repo?
> >
> > Another possible path could be to move the tests that require a Jakarta EE (full
> > or web) implementation to run, to a new integration project for each separate
> > Jakarta EE spec API project, to be implemented/improved by each separate Jakarta
> > EE spec API project and to be consumed/used by the jakartaee-tck project.
> >
> > I'll be patient now and wait for input from others, but lets not wait too long
> > to discuss, as we have volunteers waiting to help I think via [1].
> >
> > Scott
> >
> > > Scott
> > >
> > > On 4/11/19 2:20 PM, Bill Shannon wrote:
> > > > Scott Marlow wrote on 4/11/19 6:53 AM:
> > > > > Hi,
> > > > >
> > > > > I have a few question for this mailing list, related to issues#51 [1].
> > > > >
> > > > > Where should we discuss the idea of moving standalone TCK tests, out of the
> > > > > jakartaee-tck [2] repo?  Here on this mailing list or on the issue tracker [1]?
> > > >
> > > > I would say here on the mailing list.
> > > >
> > > > > My personal preference is to discuss on this email list, but I know from
> > > > > discussion on [1], that others will prefer using the issue tracker.  The reason
> > > > > why I prefer using this mailing list, is because I think email does a better
> > > > > job
> > > > > of displaying a nested discussion, than (flat) github issues.
> > > >
> > > > I agree completely.
> > > >
> > > > > One reason to use
> > > > > [1], is so that others that aren't on this email list, can participate in this
> > > > > discussion.
> > > >
> > > > Anyone can subscribe to the mailing list, and they can view the archives here:
> > > > https://www.eclipse.org/lists/jakartaee-tck-dev/
> > > >
> > > > > Scott
> > > > >
> > > > > [1] https://github.com/eclipse-ee4j/jakartaee-tck/issues/51
> > > > > [2] https://github.com/eclipse-ee4j/jakartaee-tck
> > > > > _______________________________________________
> > > > > jakartaee-tck-dev mailing list
> > > > > jakartaee-tck-dev@xxxxxxxxxxx
> > > > > To change your delivery options, retrieve your password, or unsubscribe from
> > > > > this list, visit
> > > > > https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev