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.

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

should be null and should not' (be null) are failling #52

Closed
theburningmonk opened this issue Jun 4, 2015 · 2 comments
Closed

should be null and should not' (be null) are failling #52

theburningmonk opened this issue Jun 4, 2015 · 2 comments

Comments

@theburningmonk
Copy link

Just tried these on 1.3.0.1 and both are throwing null ref exception
"123" |> should be null
"123" |> should not' (be null)
null |> should be null

using Nunit's Assert.That(null, Is.Null) works

@pver
Copy link

pver commented Jun 17, 2015

I had a similar issue with this until I noticed I forgot I had to use Null instead of null:

"123" |> should be Null
"123" |> should not' (be Null)
null |> should be Null

would be nice to have it working with 'null' as well though

alex-bogomaz added a commit to alex-bogomaz/FsUnit that referenced this issue Dec 1, 2015
alex-bogomaz added a commit to alex-bogomaz/FsUnit that referenced this issue Dec 1, 2015
alex-bogomaz added a commit to alex-bogomaz/FsUnit that referenced this issue Dec 1, 2015
alex-bogomaz added a commit to alex-bogomaz/FsUnit that referenced this issue Dec 4, 2015
alex-bogomaz added a commit to alex-bogomaz/FsUnit that referenced this issue Dec 5, 2015
sergey-tihon added a commit that referenced this issue Dec 7, 2015
Fix of #52 - add support for null in should (replacement for PR #80)
@sergey-tihon
Copy link
Member

Released in v1.4.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants