Merged
Conversation
This commit adds a new integration test suite (`tests/test_integration.py`) that provides end-to-end coverage for the application's main workflows. Key features of the new tests: - A file-based integration test that runs the `main.py` script to generate a baseline from a data file and then performs an analysis using that baseline. - A ClickHouse-based integration test that covers the full data pipeline: 1. Creates the database schema using `scripts/create_schema.py`. 2. Imports data from a file using `scripts/import.py`. 3. Runs `main.py` to generate a baseline from ClickHouse. 4. Runs `main.py` to perform an analysis from ClickHouse. - The ClickHouse test is conditionally skipped if a database connection cannot be established, allowing the test suite to run in environments without a running ClickHouse instance. This provides a high level of confidence that the entire application works as expected.
This commit introduces a GitHub Actions workflow to automatically run the test suite on push and pull request events. The CI pipeline: - Sets up a Python 3.12 environment. - Starts a ClickHouse service container to enable integration tests. - Installs all project dependencies. - Upgrades `numpy`, `pandas`, and `scipy` to versions compatible with Python 3.12. - Runs the full test suite, including unit and integration tests. This ensures that all tests are continuously run and helps maintain code quality.
Signed-off-by: Gozzim <80704304+Gozzim@users.noreply.github.com>
This commit fixes the dependency installation step in the GitHub Actions workflow. The previous implementation pre-installed upgraded packages but then ran `pip install -r requirements.txt`, which caused conflicts and build failures due to the old, incompatible versions specified in the file. The new implementation correctly handles this by: 1. Installing the compatible versions of `numpy`, `pandas`, and `scipy`. 2. Using `grep` to filter out these packages from `requirements.txt` and then installing the remaining dependencies. This ensures a stable and correct CI build without modifying the project's pinned dependencies.
Signed-off-by: Gozzim <80704304+Gozzim@users.noreply.github.com>
This commit addresses two issues: 1. Updates the GitHub Actions workflow to trigger on pushes to the `master` branch and on all pull requests, as requested. 2. Fixes the failing tests in `tests/common/test_utils.py` by updating the assertions to expect string values for the `count` field in the metric summary, which aligns the tests with the function's actual output. This ensures the CI pipeline runs on the correct events and that the entire test suite passes.
This commit improves the test coverage for several key modules by adding new tests to cover previously untested lines of code, focusing on edge cases and error handling. The coverage for the following modules has been improved: - `analyzer_lib/analysis/traceroute/parser.py` - `analyzer_lib/analysis/traceroute/path_analyzer.py` - `analyzer_lib/common/ripe_api.py` - `analyzer_lib/common/utils.py` This increases the overall test coverage of the project and improves the robustness of the test suite.
This commit adds a test coverage badge to the `README.md` file and sets up the necessary infrastructure in the GitHub Actions workflow to automatically generate and update it. Key changes: - Added `genbadge` to the development dependencies. - Updated the `README.md` to include the markdown for the coverage badge. - Modified the `.github/workflows/ci.yml` file to: - Generate a `coverage.xml` report. - Use `genbadge` to create `coverage.svg` from the report. - Commit the updated `coverage.svg` file back to the repository on pushes to the `master` branch.
This commit fixes the dependency installation step in the GitHub Actions workflow by using a more robust method. The previous approach of piping `grep` output to `pip` was not reliable. The new implementation creates a temporary requirements file that excludes the packages being manually upgraded (`numpy`, `pandas`, `scipy`) and then installs from that file. This ensures a stable and correct CI build without modifying the project's pinned dependencies.
This commit fixes the issue where the coverage badge was not being committed back to the repository. The `EndBug/add-and-commit` action requires write permissions to the repository contents to be able to push changes. The default `GITHUB_TOKEN` may not have these permissions. This change adds a `permissions` block to the CI workflow job, explicitly granting `contents: write` permission. This is the standard and secure way to allow a workflow to commit to the repository.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit adds a new integration test suite (
tests/test_integration.py) that provides end-to-end coverage for the application's main workflows.Key features of the new tests:
main.pyscript to generate a baseline from a data file and then performs an analysis using that baseline.scripts/create_schema.py.scripts/import.py.main.pyto generate a baseline from ClickHouse.main.pyto perform an analysis from ClickHouse.This provides a high level of confidence that the entire application works as expected.