Improve test coverage

[Nekroze]

Change Request

Please describe the current behaviour

At present dab does acceptance testing for all major features.

What is suboptimal about the current behaviour

The current behaviour is insufficient because there are features that are not currently tested allowing a chance of unknown regression.

Describe the way you think it should behave

Increase the number of acceptance tests to cover untested features.

[Nekroze]

To test:

• dab repo list output
• NSS DB PKI CA injection and removal with dab pki ready and dab pki destroy respectively
• app dependency resolution
• app version variables (especially for those with Dockerfiles as well)
• Can select kafka and zookeeper used by apps #242
• Dab proxy #221
• cli tool apps mount pwd where the app reads/writes files in normal operation (eg ansible)
• Dynamically generate telegraf config #143
• custom and disabled Tips #129
• Ingest log files #123
• Auto update completion binary #99
• version subcommand output
• Shell Completion Test #62
• can connect to common service apps (eg redis) on standard ports.
• should at least validate that the tour is a valid movie if not ensure the tour is up to date with the source script.

[Nekroze]

Many tests such as starting each app does not run in CI due to flake and time concerns. If this can be less flakey and made to run only after all other jobs succeed, perhaps only run a random subset of them if its still too long, it would provide better regression testing.