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
Is your feature request related to a problem? Please describe.
When debugging a test case and killing the debug process, the containers are not cleaned up, but live forever.
Describe the solution you'd like
Java testcontainers has found a solution to this by spinning up a container, that kills other containers, after the test process got killed. Maybe you can find some inspiration in their approach:
We need to have unique container name for the tests that run in parallel and exclusively use container's resource. In case we run tests in collection they are executed sequentially and we don't need unique container name. In this approach this problem would have simpler solution if Squadron allowed to override container's name with non-unique one. Unfortunately ContainerResourceBuilder does not provide us with the way to override the container name.
Is your feature request related to a problem? Please describe.
When debugging a test case and killing the debug process, the containers are not cleaned up, but live forever.
Describe the solution you'd like
Java testcontainers has found a solution to this by spinning up a container, that kills other containers, after the test process got killed. Maybe you can find some inspiration in their approach:
testcontainers/testcontainers-java#545
The text was updated successfully, but these errors were encountered: