[Question]What is the best way to access Fitnesse testsuite results from docker container?

[pb1981]

Summary of the Query:

Want to figure out the best way to access Fitnesse testsuite results from outside when results are lying inside docker container?

I have these approaches in hand

1. Mounting a docker container volume in the host PC where docker container is running but I was not successful as Java.io exceptions where getting thrown. While trying this test ensured that mounted volume has same read write access wrt same user/group but still the attempt was not successful and container kept on exiting every few seconds.

2. Fitnesse dockerised or not, exposes rest services. So the result xml files can be viewed in this URL:
   http://testserver ip:port/files/testResults/FitNesse.TestSuiteName and we have to parse the xml file content from REST GET call response to get the final count.

or
3) Web Scrap below URL to get Results Summary.
http://serverip:port/FitNesse.TestSuiteName?responder=overview

[woodybrood]

Can you tell us more about your container setup? What all is in the container. Is both fitnesse and the SUT in the container? Is FitNesse running as the wiki and being executed from outside the container? Or is it being run as a command in the container? Where is the FitNesseRoot where your tests exist? How is it updated?

[pb1981]

@woodybrood The container has the TestCases and TestResult xml files stored there. The root is like :/opt/fitnesse/FitNesseRoot/FitNesse
The Test Suite are executed by using URL like below:
http://TestserverIP:port/FitNesse.TestSuiteName?responder=suite&remote_debug=true

The SUT and Runner is outside Container .

Problem is that we can't directly read the result xml residing inside container, doing "docker cp source destination" of result files to outside path every time after the suite is executed is not a good solution I think

[fhoeben]

Do I understand correctly that your FitNesse container is 'long-lived', i.e. you want to start it once and use it for multiple runs? Do you start the runs via a browser?

I've used dockerized FitNesse only to run tests from a CI environment where I started a new container each 'build/run' based on test definitions in version control, run the tests, copy the results and then dispose of the container. This way each run is completely fresh, no side-effects from previous runs, and there is no need to keep a container running when there is no test.

In this approach I used FitNesse jUnit runner and did copy the generated XML (surefire format) and HTML test reports after each run. This worked both with mounted volumes and docker cp, but the 'cp' approach gave less permission hassle so I preferred that.

[pb1981]

Yes @fhoeben , fitnesse docker container will be long lived and also it will be used for multiple runs after it's started. I am running Test Suite through browser only.