How were the tests conducted in the CI/CD pipeline? What was monitored?

In CI/CD pipelines, tests run automatically on each commit or pull request. Typically, the following are monitored:

• Unit tests: checking the logic of individual functions and components.
• Integration tests: verifying interaction between modules and with external services.
• E2E tests: simulating user scenarios.
• Code coverage: metrics to ensure important parts of the code are tested.
• Static code analysis: checking style, potential errors, and vulnerabilities.
• Execution speed: to prevent the pipeline from slowing down development.

In Go, go test is usually used with flags for coverage and profiling. The pipeline is configured for automatic execution, and if tests fail, the build stops, preventing bugs from reaching production.