Testing strategy

[stan-dot]

It is uncertain how much do we want to test, and also what to do about the message bus in testing. We could mocking using something like microcks .

[callumforrester]

Finding a way to mock the message bus without writing loads of code would indeed be good!

As a general answer, and based on recent meetings including the DAQ away day, we currently have >90% coverage and I think we should aim to keep it that way. Virtually all of the GDA codebase is not covered and it shows.

If something breaks, and you raise a PR to fix, you should always have a test that reproduces the breaking case.

[stan-dot]

will explore with Helm

[stan-dot]

$ helm install microcks microcks/microcks --version 1.7.1 --namespace microcks --set microcks.url=microcks.$(minikube ip).nip.io --set keycloak.url=keycloak.$(minikube ip).nip.io

this uses minikube and for this I'm not sure what to use

[stan-dot]

docker-compose variant doesn't work either:

[stan-dot]

the containers go up but the endpoint is not available

[stan-dot]

potential reference issues

https://github.com/epics-containers/edge-containers-cli/blob/fb790a617028c6723ac3ad14663436759b457a7d/tests/test_system.py

https://github.com/epics-containers/edge-containers-cli/blob/fb790a617028c6723ac3ad14663436759b457a7d/.github/workflows/_sys_test.yml