Skip to content

test: Extending coverage for property based tests #220

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 29 commits into from
Jun 11, 2025

Conversation

NicoMolinaOZ
Copy link
Contributor

@NicoMolinaOZ NicoMolinaOZ commented May 13, 2025

Summary

https://linear.app/openzeppelin-development/issue/PLAT-6046/add-pbt-for-chain-specific-logic

  • Adding PBT for functions that are not being covered properly.
  • Deleting unused code (after the big refactor, I found some functions not being used anymore)

Testing Process

Checklist

  • Add a reference to related issues in the PR description.
  • Add unit tests if applicable.
  • Add integration tests if applicable.
  • Add property-based tests if applicable.
  • Update documentation if applicable.

Sorry, something went wrong.

@NicoMolinaOZ NicoMolinaOZ changed the title tests: Extending coverage for property based tests test: Extending coverage for property based tests May 13, 2025
@NicoMolinaOZ NicoMolinaOZ marked this pull request as ready for review May 13, 2025 08:13
Copy link

codecov bot commented May 13, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.3%. Comparing base (f02a137) to head (c050330).

Additional details and impacted files
@@           Coverage Diff           @@
##            main    #220     +/-   ##
=======================================
+ Coverage   95.8%   96.3%   +0.4%     
=======================================
  Files         73      73             
  Lines      24373   24225    -148     
=======================================
- Hits       23367   23333     -34     
+ Misses      1006     892    -114     
Flag Coverage Δ
integration 59.1% <57.6%> (+0.3%) ⬆️
properties 33.0% <92.3%> (+6.5%) ⬆️
unittests 87.1% <97.2%> (-0.1%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Member

@shahnami shahnami left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for the hard work!

@shahnami
Copy link
Member

shahnami commented Jun 11, 2025

@NicoMolinaOZ before merging, any idea why our overall test coverage actually is going down after this PR (95.9% -> 95.6%)

I ask because 2 days ago this PR was bumping it to 96.3 👀

Screenshot 2025-06-11 at 13 43 44

@NicoMolinaOZ
Copy link
Contributor Author

@NicoMolinaOZ before merging, any idea why our overall test coverage actually is going down after this PR (95.9% -> 95.6%)

I ask because 2 days ago this PR was bumping it to 96.3 👀

Screenshot 2025-06-11 at 13 43 44

Good catch, I didn't realize yesterday. I am running the tests again, sometimes codecov made mistakes,

@NicoMolinaOZ
Copy link
Contributor Author

@NicoMolinaOZ before merging, any idea why our overall test coverage actually is going down after this PR (95.9% -> 95.6%)

I ask because 2 days ago this PR was bumping it to 96.3 👀

Screenshot 2025-06-11 at 13 43 44

After running the tests is showing 96.3% again 👀

@NicoMolinaOZ NicoMolinaOZ merged commit 1e1df74 into main Jun 11, 2025
28 checks passed
@NicoMolinaOZ NicoMolinaOZ deleted the plat-6046-add-property-based-tests branch June 11, 2025 12:34
@github-actions github-actions bot locked and limited conversation to collaborators Jun 11, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants