GitHub user tenthe added a comment to the discussion: Implementing Integration E2E Tests for Java Client
Hi @Yuukadesu , thanks you very much for stariting for the discussion and for putting together the proposal. I had one thought regarding the tests. If I understand it correctly, the proposal currently tries to test **both the Java client itself and the load-balancing behavior** in the same E2E setup. Would it maybe make sense to **split this into two separate tests**? For example: * one **simple E2E test for the Java client**, mainly verifying that creating adapters/pipelines via the client works and that the data path (including the filter semantics) behaves correctly * a **separate test focused on load balancing**, where we specifically check the distribution of adapters and pipeline elements across the extension instances That way the client test stays relatively simple and failures might be easier to interpret. Also one small question about the broker: since **NATS is the default broker since the last release**, would it make sense to **use NATS instead of Kafka in the test setup**? These are just some thoughts I am happy to hear your opinion on this. GitHub link: https://github.com/apache/streampipes/discussions/4216#discussioncomment-16008836 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
