Commits

Commits on Jun 20, 2020

Commits on May 19, 2019

fixed ADR links
wolframkriesing
authored

Commits on May 18, 2019

A bit of docs in the tests.
wolframkriesing
committed
Add a little more safety, let's test that the goss.yaml file contains certain strings.
wolframkriesing
committed
Manually add a test that the size of the goss.yaml file is greater than (gt) 0 bytes.
wolframkriesing
committed
Don't mount the dir anymore but COPY it into the docker container and the tests pass. Yeah.
wolframkriesing
committed
Move the tests into "tests" directory and verify that the goss.yaml file is in the container.
wolframkriesing
committed
Allow to pass the last parameter to docker-run, so we can also jump into the container.
wolframkriesing
committed
A bit of usage description.
wolframkriesing
committed
Make `run.sh` start the container which contains goss and which mounts it's own image to test it :).
wolframkriesing
committed
We don't need to test all the details of the docker command, exit-status and stdout is enough.
wolframkriesing
committed
Add docker to the tests, by using `goss add command docker` which generates the expectation for us.
wolframkriesing
committed
Document a time-saving tip.
wolframkriesing
committed
Add and describe how to do dind.
wolframkriesing
committed
Mount the docker.sock, so we do NOT start the docker container with the current docker container, but we use the host's system to run it on.
wolframkriesing
committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commits on Jun 20, 2020

more explicit

moved repo

Commits on May 19, 2019

fixed ADR links

Commits on May 18, 2019

A bit of docs in the tests.

Add a little more safety, let's test that the goss.yaml file contains certain strings.

Manually add a test that the size of the goss.yaml file is greater than (gt) 0 bytes.

Don't mount the dir anymore but COPY it into the docker container and the tests pass. Yeah.

Move the tests into "tests" directory and verify that the goss.yaml file is in the container.

Allow to pass the last parameter to docker-run, so we can also jump into the container.

A bit of usage description.

Make `run.sh` start the container which contains goss and which mounts it's own image to test it :).

We don't need to test all the details of the docker command, exit-status and stdout is enough.

Add docker to the tests, by using `goss add command docker` which generates the expectation for us.

Document a time-saving tip.

Add and describe how to do dind.

Mount the docker.sock, so we do NOT start the docker container with the current docker container, but we use the host's system to run it on.

Commits on May 17, 2019

Inside the docker container `dgoss` is already installed, but if we want to test another image, we need docker to do so.

We reduce the yaml file to represent the stuff we do care about, which is not all the output, but just: exit-status, stdout, stderr and the version.

Fix the test again and see the test pass. Yeah. The shell output is:

We need to tell goss what this thing that it tests is. In our case it is a command, so we have to add this level of indentation to the file and "command:" in the first line.

We change the goss version we expect to see in the container to "0.1.6" just to see the test fail.

Mount the volume into the docker container, so we have the goss.yaml file available in there and can use `goss v` to run the tests.

Use `goss add command goss` inside the docker container, which was started by `./run.sh`.

Make sure the bash script fails on exception.

Build a docker file with goss installed in it and create a run script, which starts it up and goes into the shell inside the container.

Link the latest decisions.

The first two decisions taken.

Describe the plan.

Branch selector

User selector

Datepicker

Commit History

Commits on Jun 20, 2020

Commits on May 19, 2019

Commits on May 18, 2019

Commits on May 17, 2019