]
Kabir Khan updated WFCORE-2830:
-------------------------------
Fix Version/s: 4.0.0.Beta2
(was: 4.0.0.Beta1)
Split testsuite/shared to distinguish things meant for sharing within
the core testsuite from things usable in other projects
-----------------------------------------------------------------------------------------------------------------------------
Key: WFCORE-2830
URL:
https://issues.jboss.org/browse/WFCORE-2830
Project: WildFly Core
Issue Type: Task
Components: Test Suite
Reporter: Brian Stansberry
Fix For: 4.0.0.Beta2
The testsuite/shared module includes two conceptually different types of code:
1) Things that are meant to be usable across different modules in core's own
testsuite.
2) Things that we are willing to support for use in other projects that rely on WildFly
Core.
Since the two things are mixed, we are essentially supporting externally things that are
not intended for use outside core. And it makes it difficult to evaluate new additions to
testsuite/shared, to see whether the addition is really relevant to core and to see
whether proposed external use is something we want.
The purpose of WildFly Core is not to be a provider of testsuite utilities. For anything
we expose for external use, there should be a substantial code maintenance benefit that
comes from sharing it, something beyond avoiding code duplication.