[
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...
|
On 10/24/22 3:30 AM, Alwin Joseph
wrote:
Hi,
I have
tried to cover some of the points in wiki [1] that could be
useful while refactoring standalone TCKs into separate
repository as Junit tests. This can be improved as we get
more inputs and queries.
Thanks Alwin!
I created a pr
https://github.com/eclipse-ee4j/jakartaee-tck/pull/1129 with an
asciidoc copy of your new wiki note (stored in new notes folder).
What do you and others think about trying to store notes in the
Platform TCK repo? The advantage of storing notes directly in the
Platform TCK repo is that anyone can create a pull request which
we tried before with google pages that didn't seem as easy as just
opening the wiki page editor.
If others want to try this, we can update your new wiki page to
link to the merged pr (once merged).
IMO, this is a good idea for design notes or any notes that we
expect to last for a long time. IMO we should always use the wiki
for things like TCK status information as we want that to be
quick/easy to update.
Scott
[1]
https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Standard-Rules-while-separating-standalone-TCKs-from-platform-TCK
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#
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
