complone opened a new issue, #4499: URL: https://github.com/apache/rocketmq/issues/4499
Because in the ```5.0.0-beta``` branch, in the multi-threaded scenario, the interface belonging to DefaultMQAdmin needs to query the broker's data first, and then perform index aggregation such as: ```offset```, ```MemberGroup```, ```SubscriptionGroup``` and other attributes, and need to use related ```RemotingCommad``` communicates based on netty. When developers submit unit tests, it is difficult to reproduce pre-start ```broker```, ```namesrv``` and other processes in the local test thread, so I hope to try to migrate the IntegrationTestBase class from test moudle to tool module. But this comes with two problems 1. The original intention of ```IntegrationTestBase ```was to test the high availability of dledger replicas. The action of pre-starting the thread is prepared before the test, and then users can add or delete topics and other operations. Currently, tests such as ```BatchSendIT```, ```DLedgerProduceAndConsumeIT``` need to rely on For this class test, you need to manually change the test class after refactoring, and the involved modules also need to import the test module 2. Since ```5.0.0-beta``` needs to get some broker information from namesrv, ```rocketmq-namesrv``` needs to be added when ```IntegrationTestBase``` is migrated to the tools class to simulate actions related to namesrv - [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here, - [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here, - ... -- 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]
