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

Handle no expected value in unary assertions #43

Open
jmakeig opened this issue Sep 22, 2016 · 0 comments
Open

Handle no expected value in unary assertions #43

jmakeig opened this issue Sep 22, 2016 · 0 comments
Assignees
@jmakeig
Labels
bug
Milestone
1.0

Comments

@jmakeig
Copy link
Owner

jmakeig commented Sep 22, 2016

In assert.true() the expected value should be true. It currently comes up as undefined because it’s not being set. Presumably this happens for assert.false() and any other unary assertions.
@jmakeig jmakeig added the bug label Sep 22, 2016
@jmakeig jmakeig added this to the 1.0 milestone Sep 22, 2016
@jmakeig jmakeig self-assigned this Sep 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jmakeig jmakeig

Labels
bug
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
1 participant
@jmakeig