Package zipkin2.storage
Class ITSpanStoreHeavy<T extends StorageComponent>
- java.lang.Object
-
- zipkin2.storage.ITStorage<T>
-
- zipkin2.storage.ITSpanStoreHeavy<T>
-
public abstract class ITSpanStoreHeavy<T extends StorageComponent> extends ITStorage<T>
Base heavy tests forSpanStore
implementations. Subtypes should create a connection to a real backend, even if that backend is in-process.As these tests create a lot of data, implementations may wish to isolate them from other integration tests such as
ITSpanStore
-
-
Constructor Summary
Constructors Constructor Description ITSpanStoreHeavy()
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description protected void
configureStorageForTest(StorageComponent.Builder storage)
Configures aStorageComponent.Builder
with parameters for the test being executed.protected void
getTraces_manyTraces(org.junit.jupiter.api.TestInfo testInfo)
Formerly, a bug was present where cassandra didn't index more than bucket count traces per millisecond.protected boolean
initializeStoragePerTest()
Sets the test to initialise theStorageComponent
before each test rather than the test class.protected void
traceWithManySpans(org.junit.jupiter.api.TestInfo testInfo)
-
Methods inherited from class zipkin2.storage.ITStorage
accept, accept, assertGetTraceReturns, assertGetTraceReturns, assertGetTraceReturnsEmpty, assertGetTracesReturns, assertGetTracesReturns, assertGetTracesReturnsCount, assertGetTracesReturnsEmpty, assertGetTracesReturnsEmpty, blockWhileInFlight, checkStorage, clear, names, newStorageBuilder, requestBuilder, returnsRawSpans, sortTrace, store, testSuffix, traces
-
-
-
-
Method Detail
-
initializeStoragePerTest
protected boolean initializeStoragePerTest()
Description copied from class:ITStorage
Sets the test to initialise theStorageComponent
before each test rather than the test class. Generally, tests will run faster if the storage is initialized as infrequently as possibly while clearing data between runs, but for certain backends like Cassandra, it's difficult to reliably clear data between runs and tends to be very slow anyways.- Overrides:
initializeStoragePerTest
in classITStorage<T extends StorageComponent>
-
configureStorageForTest
protected final void configureStorageForTest(StorageComponent.Builder storage)
Description copied from class:ITStorage
Configures aStorageComponent.Builder
with parameters for the test being executed.- Specified by:
configureStorageForTest
in classITStorage<T extends StorageComponent>
-
traceWithManySpans
@Test protected void traceWithManySpans(org.junit.jupiter.api.TestInfo testInfo) throws Exception
- Throws:
Exception
-
getTraces_manyTraces
@Test protected void getTraces_manyTraces(org.junit.jupiter.api.TestInfo testInfo) throws Exception
Formerly, a bug was present where cassandra didn't index more than bucket count traces per millisecond. This stores a lot of spans to ensure indexes work under high-traffic scenarios.- Throws:
Exception
-
-