You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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. opengeospatial/ets-common#2
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.
The text was updated successfully, but these errors were encountered: