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
We'd like to ensure that any interactions with the system test cluster and associated resources are done in a thread safe way.
Analysis
The system test cluster and associated resources are currently deployed in SleeperSystemTestExtension.beforeAll. This is actually called many times, once for each test class. We can either make that thread safe, or move it to the initialisation of SystemTestDeploymentContext.
The SystemTestDeploymentContext is held in a static constant for each test type (in memory, LocalStack or deployed), so if we don't mutate anything after that is constructed, it will be thread safe.
We can adjust DeployedSystemTestResources to avoid any mutable fields on the class.
The text was updated successfully, but these errors were encountered:
Background
Split from:
Description
We'd like to ensure that any interactions with the system test cluster and associated resources are done in a thread safe way.
Analysis
The system test cluster and associated resources are currently deployed in
SleeperSystemTestExtension.beforeAll
. This is actually called many times, once for each test class. We can either make that thread safe, or move it to the initialisation ofSystemTestDeploymentContext
.The
SystemTestDeploymentContext
is held in a static constant for each test type (in memory, LocalStack or deployed), so if we don't mutate anything after that is constructed, it will be thread safe.We can adjust
DeployedSystemTestResources
to avoid any mutable fields on the class.The text was updated successfully, but these errors were encountered: