Testing Ozone

This section documents how to run and modify tests against Ozone.

📄️ Unit Tests

Unit tests are the foundation of Ozone's testing strategy, focusing on validating the behavior of individual classes and methods in isolation. They are fast, reliable, and essential for detecting issues early in the development process.

📄️ Integration Tests

Integration tests validate how multiple components of the Ozone system work together. They are more comprehensive than unit tests but run in a more controlled environment than full acceptance tests.

📄️ Acceptance Tests

Acceptance tests validate the complete Ozone system from an end-user perspective. They deploy and test Ozone in a containerized environment that closely resembles real-world deployments.

📄️ Continuous Integration

Apache Ozone uses GitHub Actions for continuous integration (CI), automating the build, test, and verification processes. This ensures code quality and reduces the risk of introducing defects.

📄️ Static Analysis

Apache Ozone uses static code analysis tools to identify potential bugs, code smells, security vulnerabilities, and other issues before they make it into production. SonarQube is the primary tool used for comprehensive code quality analysis.