|Re: [jakartaee-tck-dev] [External] : Re: standard recipe to follow for refactoring the Platform TCK tests...|
IMO, Platform TCK refactoring should be targeted on SPEC basis for a particular Jakarta EE release, refactoring all of platform TCK is a huge effort and not feasible for a single Jakarta EE release.
Common TCK framework needs to be implemented for the refactored TCK's, some of the common functionality are as follows:
1) Signature test Driver and recording of new Signature.
2) Logging framework for TCK.
3) Test grouping to implement common grouping like SE/EE.
4) Test exclusion.
5) Framework for seamless run of refactored standalone tests in a container for Platform runs.
6) Test execution report.
We should also explore on feasible of a common framework to encapsulate from vendors the test tech Junit/TestNG/Arquillian.
From: jakartaee-tck-dev <jakartaee-tck-dev-bounces@xxxxxxxxxxx> on behalf of arjan tijms <arjan.tijms@xxxxxxxxx>
Sent: 08 October 2022 16:00
To: jakartaee-tck developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>
Subject: [External] : Re: [jakartaee-tck-dev] standard recipe to follow for refactoring the Platform TCK tests...
On Saturday, October 8, 2022, Emily Jiang via jakartaee-tck-dev <jakartaee-tck-dev@xxxxxxxxxxx> wrote:
Yes, that specifically applies to the json and _expression_ language tcks, which run outside runtimes such as open liberty now.
Back to the top