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

Config.xml required, not present, and not built #347

Open
ajanett opened this issue May 31, 2018 · 2 comments
Open

Config.xml required, not present, and not built #347

ajanett opened this issue May 31, 2018 · 2 comments
Assignees
Labels
Projects

Comments

@ajanett
Copy link

ajanett commented May 31, 2018

Team Engine appears to require config.xml to be present, even when running in standalone mode with the te-install test.bat and specification of the specific test suite ctl file within $TE_BASE.
If config.xml is not present, a page full of java errors is the result. Also the stand alone operation of Team Engine does not build config.xml when it is missing.

Upon starting Team Engine under Tomcat, the config.xml file is built by the Team Engine .war starting up (if it was not present). One can then shut down the Tomcat server and noticing the config.xml is present within $TE_BASE and at then the standalone operations will work.

Is there a way to get Team Engine to construct the config.xml file without starting it under Tomcat?

@dstenger
Copy link
Contributor

dstenger commented Jun 1, 2018

You are using Command Line Interface to execute TEAM Engine, right (teamengine-console)?

In this case, the config.xml has to be generated manually and there is no automatic mechanism. However, all test suites provide a snippet in scripts folder which can be copied to config.xml.

I recommend using the Web Browser Interface or REST API to execute the test suites. However, both of them base on the war-archive which requires a tomcat. The Docker project [1], however, makes installation very easy.

[1] https://github.com/opengeospatial/teamengine-docker

@dstenger
Copy link
Contributor

@ajanett Are there any open questions remaining? Otherwise, the issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
CITE
  
Waiting
Development

No branches or pull requests

2 participants