shashankhs11 commented on PR #20392: URL: https://github.com/apache/kafka/pull/20392#issuecomment-3240659815
> a good approach would be to first split up the work to update all integrations test, before we merge any actual code changes from my analysis, I have identified these integration tests that requires update. - `RestoreIntegrationTest.java` - `EosIntegrationTest.java` - `SmokeTestDriverIntegrationTest ` - `PauseResumeIntegrationTest ` - `KafkaStreamsTelemetryIntegrationTest ` I think it would be best for us if we split this updates into 2 seperate tasks for each of us to work on ### Task 1 - [ ] `RestoreIntegrationTest.java` - [ ] `EosIntegrationTest.java` ### Task 2 - [ ] `SmokeTestDriverIntegrationTest ` - [ ] `PauseResumeIntegrationTest ` - [ ] `KafkaStreamsTelemetryIntegrationTest ` We can further also have one PR per integration test to make it cleaner and easier to review. I can pickup Task 2 to get started with and @janchilling can pick up Task 1? Does this sound like a good plan? Please feel free to add if I have missed anything. -- 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: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
