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

Support for Should-BeNullOrEmpty #39

Closed
wants to merge 6 commits into from
Closed

Conversation

stack72
Copy link

@stack72 stack72 commented Jan 27, 2013

Added a small function to the future Assertions to aupport Should-BeNullOrEmpty. This is a very useful little function.

It has a few rudimentary tests to support it working with strings and arrays

Addition of support for Should-BeNullOrEmpty
Added a check to make sure that the array > 0 when throwing the failure. We want to make sure we are covering the case where there is an element in array when there shouldn't be
Added the ability to make sure that a collection or a string has some sort of a value.
Arranged the tests into contexts. So strings and arrays are tested in the same context
Added Contexts to group the test types for clarity
@scottmuc scottmuc closed this in 08e1918 Jan 30, 2013
@scottmuc
Copy link
Contributor

Sorry Paul for not merging in your work. I tried adding your feature using the new assertion syntax. Let me know if you think it solves your requirements.

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

Successfully merging this pull request may close these issues.

2 participants