| Re: [jakartaee-platform-dev] TCK tests in the same repo as API and Spec |
Ok, I have an MVP of what I have in mind, along with pending PRs on all of the corresponding repos.3) I've created a new aggregator module in the jakartaee-tck repo, which can be the single point where we pull in all of the externalized TCK tests. Each spec shares a small portion of pom.xml to pull in the TCK dependency, and then each vendor can implement a <profile> block to run the tests with their runtime.
_______________________________________________On Tue, Feb 4, 2020 at 5:26 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:Emily Jiang wrote on 2/4/20 8:12 AM:
> I don't think the goal of breaking TCKs from the big bucket is to use a
> different test framework. I envisage the same test framework should be
> retained at least for the first release.
I agree, just as a way of reducing risk for the first release.
> I don't think using different test framework is something we should ban
> either. We should allow different specs to use a suitable test framework if
> there is strong benefit associated with the new test ramework.
I'd love to see a JUnit test runner that can run JavaTest tests, if that's even
possible. That would allow us to move to a more commonly used test framework
while preserving the many, many, existing tests. I suspect it's a lot harder
than I'm imaging, however... :-(
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev