How are tests organized in the team — who writes what, what coverage, is there E2E?

In mature Go teams, a multi-layered testing strategy is usually employed:

• Unit tests: cover individual functions and methods, providing fast and isolated testing. Written by developers, coverage typically aims for 70-90%.

• Integration tests: verify interactions between components, such as working with databases or external services.

• E2E (end-to-end) tests: simulate user behavior or the complete system workflow. They can be written using external tools (e.g., Selenium, Cypress) or specialized frameworks.

Responsibility distribution:

• Developers write unit and integration tests for their modules.
• QA or dedicated automation engineers may handle E2E tests.

Test coverage and quality are regularly analyzed, and tests are run in CI/CD pipelines to prevent regressions.