Run test suite at container startup

[nuest]

Is it possible to run a test suite at the startup of a Docker container?

I've found this example but wonder if there is a way this could be supported out of the box for all services.

Something like

docker run --rm -it -e TEST_ENDPOINT=http://localhost:8080/wms opengis/teamengine-ets-wms-13 run-all.sh

I don't see how Running a test-suite non-interactively could be done in the container. Ideally the exit status would communicate the test result.

[Disclaimer: I'm a teamengine noob, and also not able to contribute extensively myself. Just would play around with this if it's available easily.]

What would this be useful for?
One could pull the image and run the above command in an automated test environment after building the web service.

[dstenger]

First, it should be stated that TEAM Engine supports 3 different types of APIs:

• Command shell
• Web Browser Interface
• REST API (new)

The teamengine-docker project concentrates on Web Browser Interface and REST API. Thus, Command shell interface has never been tested with this project. As far as I understand, your example refers to the Command shell interface.

For your purpose the REST API should be the best fitting interface. Please review the documentation on https://opengeospatial.github.io/teamengine/users.html.

If you have any further questions regarding the different APIs or the teamengine-docker project, please feel free to ask.

[dstenger]

Of course, when the Web Browser Interface and REST API shall be used, the container serves a running application server.
In your example, just a command is executed via Docker (no running server instance afterwards).
If this is an important requirement for you, we should create an issue to enable the Command shell interface for this project.

[aaime]

@dstenger would the REST interface work for all tests suites, including the older ones?

[dstenger]

In general, the REST interface also works with older test suites. However, it has to be enabled for each test suite individually. Thus, it depends on the test suite if it works.

Please see REST interface of Beta environment giving a good overview of test suites with enabled REST interface: http://cite.opengeospatial.org/te2/rest/suites/

[aaime]

Ok, so I see it's missing for WFS 1.1, for all WCS versions, and CSW 2.0.2 (among the ones that I'd care about, at least). Is it hard to add?

[dstenger]

Enabling REST API is already covered by issues in target issue trackers:

• WFS 1.1 (status: Must be tested and can be merged then): Enable test execution using a RESTful API ets-wfs11#84
• WCS 2.0 (status: Is already merged but not installed on Beta, yet): Enable test execution using a RESTful API ets-wcs20#72
• WCS 1.1 (status: I just created the issue): Enable REST API ets-wcs11#50
• WCS 1.0 (status: I just created the issue): Enable REST API ets-wcs11#50
• CSW 2.0.2 (status: I just created the issue): Enable REST API ets-csw202#33

In general, it is not hard to implement. Please see referenced issues for instructions.
Of course, any help is welcome.

[dstenger]

Telcon @ghobona and @dstenger

Since the Docker Container exposes REST API endpoints it is already possible to create scripts which use the REST API.
We invite other developers to help us creating this enhancement.