oscarArismendi commented on issue #2148:
URL: https://github.com/apache/iggy/issues/2148#issuecomment-4366579050

   After digging into it, I’m planning to split the migration into three PRs 
for the common tests I found
   
   1. Stream Lifecycle
   Likely the most important tests across SDKs, covering shared functionality 
between:
   
   | SDK | Existing test file |
   |-----|--------------------|
   | Node.js | `foreign/node/src/e2e/tcp.stream.e2e.ts` |
   | Python | `foreign/python/tests/test_iggy_sdk.py` → `TestStreamOperations`, 
`TestErrorHandling` |
   | Java | 
`foreign/java/java-sdk/src/test/java/org/apache/iggy/client/blocking/StreamClientBaseTest.java`
 |
   | C# | `foreign/csharp/Iggy_SDK.Tests.Integration/StreamsTests.cs` |
   | Go | `bdd/go/tests/tcp_test/stream_feature_*.go` |
   
   2. Consumer Group Lifecycle
   
   | SDK | Existing test file |
   |-----|--------------------|
   | Node.js | `foreign/node/src/e2e/tcp.consumer-group.e2e.ts` |
   | Python | `foreign/python/tests/test_iggy_sdk.py` → `TestConsumerGroup` |
   | Java | 
`foreign/java/java-sdk/src/test/java/org/apache/iggy/client/blocking/ConsumerGroupsClientBaseTest.java`
 |
   | C# | `foreign/csharp/Iggy_SDK.Tests.Integration/ConsumerGroupTests.cs` |
   | Go | `bdd/go/tests/tcp_test/consumers_feature_*.go` |
   
   3. Message Polling Strategies
   
   | SDK | Existing test file |
   |-----|--------------------|
   | Node.js | `foreign/node/src/e2e/tcp.consumer-stream.e2e.ts`, 
`tcp.send-message.e2e.ts` |
   | Python | `foreign/python/tests/test_iggy_sdk.py` → 
`TestMessageOperations`, `TestPollingStrategies` |
   | Java | 
`foreign/java/java-sdk/src/test/java/org/apache/iggy/client/blocking/MessagesClientBaseTest.java`
 |
   | C# | `foreign/csharp/Iggy_SDK.Tests.Integration/SendMessagesTests.cs`, 
`FetchMessagesTests.cs` |
   | Go | `bdd/go/tests/tcp_test/messages_feature_send.go` |


-- 
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]

Reply via email to