Open dstenger opened 6 years ago
Please also note that ets-common may be a factor and may be causing multiple versions of TEAM Engine to be included in to the ETS test suites. https://github.com/opengeospatial/ets-common/issues/2
I agree with the approach. Please @dstenger @lgoltz proceed with the extraction / restructuring of the jars.
Currently, all test suites using TestNG have a dependency to TEAM Engine jar which provides required interfaces (e.g. TestSuiteController). This can lead to dependency problems as all test suites have to be updated after a new TEAM Engine release. If this update is not done, single test suites might base on outdated versions of TEAM Engine while they are running in a newer version.
My proposal is to extract those interfaces to a new project (e.g. teamengine-ets-api or teamengine-api) which can be used by TEAM Engine and test suites then. By this, we remove the dependency of all test suites to TEAM Engine.