-
Notifications
You must be signed in to change notification settings - Fork 26
Missing Spec Challenge #7
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
Comments
That's a cool idea, but the spec doesn't pass for me for the original |
You're right, my bad, I ended up pushing a version of the spec where I was testing a bidirectional assertion. Can you try it again with one direction ? EDIT : Alternatively, you can also make the bidirectional assertion work by excluding the scenario where one of the voted addresses is the current winner :
|
Because this didn't work for me, I made #12 instead. Would you agree that it's more general? |
Both of the rules above work (you can check the runs for more details). Can you share links to runs where it didn't work for you? As for your rule set, I tried it and it seems to catch the bug introduced by my mutation as well 👍 |
Nice work, this is missing spec #2. |
BordaMissingRule.spec
on the originalBorda.sol
: https://prover.certora.com/output/33434/d7f15af5748b43a38eebb1e07f1ba79e/?anonymousKey=8799eb540328477c469b5c8584b792b10ef9af32Borda.spec
onBordaNewBug.sol
: https://prover.certora.com/output/33434/ad728d166f6e4ae6a9d144407c7eae65/?anonymousKey=6f6735dba598be65de68b3c84d935a4706205331BordaMissingRule.spec
onBordaNewBug.sol
: https://prover.certora.com/output/33434/bee54e17460f471fba4613b08294725d/?anonymousKey=3dbed3eabc5884bea4c52da4b59eda0730d79f44The text was updated successfully, but these errors were encountered: