[SMTChecker] Make command line tests aware of SMT solvers
- Dominant language
- C++
- Stars
- 25.7k
- Forks
- 6.2k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 21
Description
The issue that https://github.com/ethereum/solidity/pull/8470 fixes is that the command line tests run the SMTChecker docs examples but are not aware whether there is a solver available or not, which makes it hard to decide on the test message to use:
- `This will report a warning`: this happens if there are no solvers available or the SMTChecker reports an assertion violation
- `This will not compile`: disables the test and is currently used there
Contributor guide
Research direction
Locate the command line tests that run the SMTChecker documentation examples and inspect how solver availability and expected messages are currently handled. Verify the behavior with and without an available solver; done means the tests choose the appropriate warning or disabled expectation in each case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, solidity
- Domain
- cli, compilers, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100