🧪 Add smoke tests to CI pipeline#6
Merged
Merged
Conversation
- Remove chi-square fairness check that was too strict for CI purposes - Keep improvement ratio as the primary correctness gate (start/end distance) - Remove unused functions: nearest_peak_stats, chi_square_p_value, estimate_expected_peak_probs - Clean up CLI args: remove --alpha, --min-expected, --fair-samples
- Replace pip with uv for faster, reproducible dependency management - Add astral-sh/setup-uv@v4 action for uv installation - Add smoke test steps for 3-peak and 7-peak scenarios - Use uv run for pytest and smoke test execution
- Delete test_setup.py, test_day2.py, test_day3.py from repo root - These were ad-hoc verification scripts, now superseded by proper tests
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
2 participants
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.
What does this PR do?
Adds robust smoke tests to the CI pipeline that verify the diffusion evolution algorithm is working correctly. The tests measure improvement ratio (how much closer the population gets to peaks) rather than using overly strict statistical checks that would make CI flaky.
Details