You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Modify the standard container tests to work in this repository.
Motivation and context
The standard test harness doesn't play nice with the way Admiral is composed. The configuration expects a main container and version container from which to derive tests. But that causes complications.
Admiral's composition does not have a main container. Instead, a template is used to replicate workers. Because there is no main container, it's not possible for the tests to verify an output or clean exit. We need to find a way to test the replica containers instead.
Implementation notes
First commits #5 should reference which tests need to be implemented.
Acceptance criteria
The main container tests inherited from skeleton-docker have been implemented and fully pass.
This commit instantiates a Docker client with the Docker Compose file path and the
project name. It also comments out the main container configuration,
which causes tests to fail per #6.
king-alexander
removed
the
blocked
This issue or pull request is awaiting the outcome of another issue or pull request
label
Sep 8, 2023
💡 Summary
Modify the standard container tests to work in this repository.
Motivation and context
The standard test harness doesn't play nice with the way Admiral is composed. The configuration expects a main container and version container from which to derive tests. But that causes complications.
Admiral's composition does not have a main container. Instead, a template is used to replicate workers. Because there is no main container, it's not possible for the tests to verify an output or clean exit. We need to find a way to test the replica containers instead.
Implementation notes
Acceptance criteria
The text was updated successfully, but these errors were encountered: