tkalkirill commented on code in PR #6226:
URL: https://github.com/apache/ignite-3/pull/6226#discussion_r2195242523
##########
modules/storage-api/src/testFixtures/java/org/apache/ignite/internal/storage/impl/TestMvTableStorage.java:
##########
@@ -423,4 +426,14 @@ private void busy(Runnable action) {
private String createStorageInfo() {
return IgniteStringFormatter.format("tableId={}",
tableDescriptor.getId());
}
+
+ /**
+ * Sets the {@link TestMvPartitionStorage} factory. Useful when you need
to change the behavior of a method in a test, for example. If
+ * you use setting mock stubs after creating a storage, you can get into a
race and as a result get {@link UnfinishedStubbingException}.
+ *
+ * <p>After running a test or test class, you must set the {@link
TestMvPartitionStorageFactory#DEFAULT}.</p>
Review Comment:
`BaseIgniteAbstractTest` doesn't know anything `TestMvTableStorage`, I don't
think it's a good idea.
In general, we can do this for `ClusterPerClassIntegrationTest` and
`ClusterPerTestIntegrationTest`, what do you think?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@ignite.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
