Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Expect and Should have unexpected behavior with parens and .be.true or .be.false #53

Closed
anachronic opened this issue Nov 20, 2019 · 0 comments
Closed

Expect and Should have unexpected behavior with parens and .be.true or .be.false #53

anachronic opened this issue Nov 20, 2019 · 0 comments

Comments

@anachronic
Copy link

Allow me to explain.

The following assertion fails as expected:

        True | should.be.false

Neither of the following fail:

        expect(True).to.be.false
        should(True).be.false

I think this is a bug, and I'd love to contribute if pointers are given
sgissinger added a commit to sgissinger/grappa that referenced this issue Nov 16, 2020
@sgissinger
Seems to solve grappa-py#53
177839a 
Make run_accessor matches run_matcher code. The error may be on line 34 where self.test._trigger() wasn't trigger.
@sgissinger sgissinger mentioned this issue Nov 16, 2020
Closed
@h2non h2non closed this as completed in fbaf340 Nov 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@anachronic