Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent dependencies of test suites to TEAM Engine #335

Open
dstenger opened this issue Apr 23, 2018 · 2 comments
Open

Prevent dependencies of test suites to TEAM Engine #335

dstenger opened this issue Apr 23, 2018 · 2 comments
Projects

Comments

@dstenger
Copy link
Contributor

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.

@ajanett
Copy link

ajanett commented Sep 18, 2018

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

@bermud
Copy link
Contributor

bermud commented Sep 19, 2018

I agree with the approach. Please @dstenger @lgoltz proceed with the extraction / restructuring of the jars.

@dstenger dstenger added this to To do in CITE via automation May 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
CITE
  
To do
Development

No branches or pull requests

4 participants