We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
basilisp.test/is is misreporting the expected value to be falsy when is asserting a function or falsy value:
basilisp.test/is
FAIL in (issue) (issue_test.lpy:6) Test failure: false expected: false actual: false
To reproduce
tests/basilisp/issue_test.lpy
(ns tests.basilisp.issue-test (:require [basilisp.test :refer [deftest is testing]])) (deftest issue (is (some #{7} #{10 11})))
nil
(not nil)
$ poetry run pytest -k issue ================================================= test session starts ================================================= configfile: pyproject.toml plugins: anyio-4.4.0, basilisp-0.1.0, pycharm-0.7.0 collected 3334 items / 3333 deselected / 1 selected tests\basilisp\issue_test.lpy F [100%] ====================================================== FAILURES ======================================================= ________________________________________________________ issue ________________________________________________________ FAIL in (issue) (issue_test.lpy:6) Test failure: (some #{7} #{10 11}) expected: nil actual: nil =============================================== short test summary info =============================================== FAILED tests/basilisp/issue_test.lpy::issue
PR to follow.
The text was updated successfully, but these errors were encountered:
test/is
f1ec6b7
Successfully merging a pull request may close this issue.
Hi,
basilisp.test/is
is misreporting the expected value to be falsy when is asserting a function or falsy value:To reproduce
tests/basilisp/issue_test.lpy
file with a falsy function callnil
where in fact should be(not nil)
:PR to follow.
The text was updated successfully, but these errors were encountered: