FWD » Build and Source Control

The most obvious frameworks to consider are JUnit and TestNG.

Comparing JUnit and TestNG:

https://www.baeldung.com/junit-vs-testng
https://www.javacodegeeks.com/2016/09/junit-vs-testng-testing-framework-choose.html

A quick summary:

• Both frameworks have the same core features and both are used enough to be reasonable choices.
• JUnit
  • Was made first and is much more popular.
  • Has caught up with TestNG from a feature perspective in most cases.
  • Is better for:
    • running tests
    • community/support
• TestNG
  • Has the benefit of being designed later and taking lessions from early JUnit versions.
  • It is less popular which means it is not as well supported.
  • Is better for:
    • test grouping
    • provides hooks for suite and group level pre/post processing
    • a limited form of dependencies (still not very good, IMO)
    • parallelism
    • built-in reports for the output

Functionally, one would probably lean toward TestNG but JUnit is really universal so there is a definite advantage there.

Integration Testing

A separate question is whether JUnit or TestNG are also suitable for integration testing. A few articles:

https://stackoverflow.com/questions/2584629/how-can-i-specify-junit-test-dependencies
https://github.com/junit-team/junit4/wiki/Assumptions-with-assume
https://stackoverflow.com/questions/284774/can-we-use-junit-for-automated-integration-testing

My assessment is NO. Although there are some lightweight test dependency capabilities and TestNG has grouping + parallelism, neither framework is really designed for sequences of tests, let alone the multi-user complex business flows that we need. The Harness is far superior for that kind of testing.

I am OK using one of these frameworks for pure unit tests in FWD. But we won't be using them for more complex test scenarios.