Implementing Integration E2E Tests for Clients (Java, Python, Go)

[tenthe]

Introduction:

As our project continues to expand, ensuring the reliability and interoperability of our clients (Java, Python, and Go) becomes increasingly critical. Currently, our testing strategy predominantly relies on Cypress E2E tests, but it's essential to extend this to include testing of our clients.

Proposal:

I suggest initiating a discussion to explore the implementation of integration end-to-end (E2E) tests for our clients. These tests will ensure that our clients interact effectively with a running REST API, detecting any potential issues early on. We can include these tests in our nightly test runs, either before or after the Cypress tests.

Points for Consideration:

1. Testing Strategy: How can we effectively test the interoperability of our clients with a running REST API?
2. Integration with Nightly Tests: What is the best approach for integrating these E2E tests into our existing nightly test runs?
3. Cross-Language Testing: Considering we have clients in Java, Python, and Go, how can we ensure consistency across different programming languages?

Proposed Plan:

1. Discussion and Brainstorming: Let's gather ideas and insights on how to implement integration E2E tests effectively.
2. Evaluation of Testing Tools: Assess various testing tools and frameworks suitable for our clients' integration E2E testing needs.
3. Infrastructure Setup: Determine the setup requirements for running E2E tests alongside our nightly test suite.

Open Discussion:

Please share your thoughts, suggestions, and experiences regarding the implementation of integration E2E tests for our Java, Python, and Go clients.
I look forward to discussing your ideas.

[bossenti]

E2E tests for Go are planned to be part of our OSPP challenge: https://summer-ospp.ac.cn/org/prodetail/24fc00534?lang=en&list=pro

[wyyolo]

Hi, I'm interested in this task and will try to complete the E2E tests for Go.

[tenthe]

Okay, great. If you need help, let us know.
You can also create a separate issue for this so we can discuss it there.