|
Maybe we should make a choice here and create a new TCK based on those
tests and the Mojarra tests, with a selection of tests taken from the
existing TCK which we are reasonably able to convert?
That would be great indeed but also requires a lot of work.
Even if we only do 100 basic tests for the start, setup a framework and 100 tests is a lot of work.
Not sure how you implemented your tests but i like the way how it is in MyFaces.
We start a servlet mock, MyFaces+OWB for each test.
I dont think we could just copy the tests to a TCK.
Does a JakartaEE API need a TCK?
Dont get me wrong, i would like to have one but the work on FacesAPI and the impls is currently way more important. The ecosystem isnt that big anymore.
The less amount we spend into a TCK, the more time we have for the FacesAPI/Impl.
Hi,
Maybe ask the web for new Open source contributors?
TomEE does that and they do at least translations of docs and samples.
TCK is of course ways harder.
Yes, although technically it's not even super hard. It's more that the obscurity of the TCK makes it hard to get into, and hard to run and debug each test individually.
We had some very good contributions from the community to help in converting the spec document, but can we find enough people to convert thousands and thousands of tests?
Not sure...
What about ManagedBeans? How many tests (in %) uses it?
A careful estimation is that it's about the same as tests using JSP.
Im almost also sure that noone runned the TCK for MyFaces since some years. We have over 1600 unittests which are facelets only and also uses CDI.
Maybe we should make a choice here and create a new TCK based on those tests and the Mojarra tests, with a selection of tests taken from the existing TCK which we are reasonably able to convert?
Kind regards,
Arjan Tijms
faces-dev mailing list
faces-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/faces-dev
