Add tests to epiphany-wrapper-poc

[mkyc]

Is your feature request related to a problem? Please describe. Current version (0.0.1) of epiphany-wrapper-poc does not have any tests.

Describe the solution you'd like Implement resonable amount of tests.

Describe alternatives you've considered No alternatives.

Additional context None.

[plirglo]

• Create automation for unit tests (VSTS, run every command and compare results with expected state)

• Create automation for end-to-end tests (VSTS, build clusters for every platform, check state with serverspec, and compare with desired state)

[mkyc]

@plirglo first point is ok, but second is not :) If you watched demo I've been doing yesterday we do not have epiphany itself moved to docker components so I cannot test it. It is also not interest of that wrapper if docker container it started can do its job correctly or not. This wrapper only focuses on running containers in the way they should be started and react on their exit codes.

[plirglo]

So end-to-end test should contains: running container and check if exit code meets expected one, correct?

[mkyc]

Yeah. Something like this.

[mkyc]

PR in remote repo created: https://github.com/mkyc/epiphany-wrapper-poc/pull/1

This PR introduces:

• 77 new test scenarios
• unified logging
• separation to log levels and --debug flag
• license checking
• multiple other code improvements

There are unit tests and integration tests which start with make build and then tests application as separate binary.

[mkyc]

FYI, repo is moved to epiphany organisation and that means that it will not build until naming is fixed there.

[mkyc]

Testing depends on #1572

[przemyslavic]

There are 77 test cases prepared. To execute the tests, run the command make test The tests have been integrated into the CI/CD pipeline and are triggered by PRs.