Skip to content

Persisting container across multiple test classes #140

@BLZB0B

Description

@BLZB0B

Hi,

Our project (like most others) has several scala test classes. the behaviour I'm seeing when running sbt test is that our postgres container spins up, runs the tests for one class, shuts down the container, spins up another (identical) container for the next class, runs tests, shuts down etc etc for every test class (all in the same test folder). the side effect of this is our CI server is taking over an hour to build / test each project.. most of this time is waiting for postgres to start up on each new container.

is there a way to spin up the container on the first test and only when all tests in all classes have been run, then shut down?

thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions