linghengqian commented on issue #6882: URL: https://github.com/apache/incubator-seata/issues/6882#issuecomment-2380710950
> @linghengqian What are the scenarios for using the org.apache.seata:seata-mock-server dependency? The org.apache.seata:seata-mock-server was originally designed to facilitate testing the full transaction process on the SDK side for the Seata project itself. Does ShardingSphere also require such mock functionality? @slievrly - I'm guessing I made a further inference wrong about https://github.com/apache/incubator-seata/issues/5343#issuecomment-1432368918 ? I thought Seata Server would expose a startup class for Seata Server used for testing, just like the `org.apache.curator.test.TestingServer` located at https://github.com/apache/curator/blob/apache-curator-5.7.1/curator-test/src/main/java/org/apache/curator/test/TestingServer.java . - The core reason why ShardingSphere actively simulates Seata Server is that ShardingSphere only uses Docker Engine in integration testing, e2e and nativeTest. Any normal unit testing with the default Maven Profile is designed not to use Docker Engine. That's why `org.apache.shardingsphere.transaction.base.seata.at.fixture.MockSeataServer` in https://github.com/apache/shardingsphere/blob/95c98e0b72746a3520ffb81efc9160ab6522d8bd/kernel/transaction/type/base/seata-at/src/test/java/org/apache/shardingsphere/transaction/base/seata/at/fixture/MockSeataServer.java exists. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
