projects / cvc5.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3f1ab56) | patch
A proposal for python api unit tests (#6255)
authoryoni206 <yoni206@users.noreply.github.com>
Mon, 5 Apr 2021 13:30:19 +0000 (06:30 -0700)
committerGitHub <noreply@github.com>
Mon, 5 Apr 2021 13:30:19 +0000 (13:30 +0000)
commit6c2779e52f1301d99b874897f902e31d4a8cc208
tree5e7d1c5c11d8114bca03a5009031412405712a80tree
parent3f1ab5672ca746a4a6573e1ebf9f74d72978d1cfcommit | diff
A proposal for python api unit tests (#6255)

This PR introduces two unit tests for the python api, translated directly from the unit tests for the cpp api.
The goal is to get feedback in order to reach some kind of a pattern/style for python API tests.
Also, i'd be happy to hear if there is any specific cpp api unit test I should translate for this initial attempt (e.g., a test that is more representative or might raise difficulties). For now i just picked the first two solver tests.
test/CMakeLists.txt diff | blob | history
test/python/CMakeLists.txt [new file with mode: 0644] blob
test/python/unit/api/__init__.py [new file with mode: 0644] blob
test/python/unit/api/test_solver.py [new file with mode: 0644] blob