[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-tck-dev] [External] : standard recipe to follow for refactoring the Platform TCK tests...
|
We certainly need an extraction of the expertise needed to transform tests into the Junit environment, so any starting point would be helpful.
Hi Scott,
Â
- For Faces, Security and Authentication we did not transform the tests to Junit. We only used maven-ant-run plugin to build
and run the Javatests after lifting the required source files.
- REST, JSONB/P tcks were migrated to Junit tests for EE10. Some of the steps followed to convert the tests to Junit for REST
is documented in [1]. This might not be a standard procedure that could be used for all other TCKs. I can try to list out the common steps and requirements to be followed for other TCKs in a wiki.
Â
Â
Regards,
Alwin
Â
[1]
https://github.com/alwin-joseph/rest/wiki/REST-TCK-separation-from-JakartaEE-TCK-repo.
Â
Â
Â
Hi,
It would be good to have a standard recipe to follow for refactoring the Platform TCK tests as we discussed on the TCK call [1] this week.
What are the initial steps that we followed for EE 10 to refactor Platform TCK tests to junit? For the Faces TCK refactoring I recall we discussed a lot on Faces issues (e.g. like how to deal with vendor deployment descriptors). Does anyone feel ready
to respond with what the steps might be?Â
Or should we explore those further together (pick a test bucket and start refactoring at least one test in the Platform TCK)?Â
Scott
[1]
https://docs.google.com/document/d/1V1dDLJkd14EDRMPeuI0VzPtU4Lbli8FFBd1pLDLlOrY/edit#