[jakartaee-tck-dev] Follow up on Junit5 versus TestNG discussion...

[Scott Marlow <smarlow@xxxxxxxxxx>]

There were many good points about the merits of Junit5 versus TestNG brought up on the TCK calls yesterday.  Quoting from the second call minutes:

"

• It would be better to not mix different test harness frameworks

  • Having too many different technologies is a problem.

    • Having the tests be complicated due to multiple test harnesses will make long term maintenance harder.

    • Limiting the choice of test harnesses will help implementations that are dealing with test failures.

    • Simplify up front the tests by using a single technology.

  • We should discuss this specific topic of whether to allow mixing of test harness technologies on the Platform TCK mailing list

    • Outcome will be to pick one or decide to allow more than one.

"

Below are some points that might help us to discuss which test harness to use in the Platform TCK (please add additional points that you would like to discuss):

1. Pick the test harness that is easier for TCK users to work with.
2. Pick the test harness that is easier to develop tests for and maintain those tests over a long period of time.
3. Pick the test harness that is easier to automatically script refactoring of existing Platform TCK tests for.
   

Scott