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
This is out current output:
expect([0,1,2,3,4,5,6,7,8,9], 'to contain', [0,1,3,4,5,6,7,8,9]) UnexpectedError: expected [ 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 ] to contain [ 0, 1, 3, 4, 5, 6, 7, 8, 9 ]
It would be better if we did the following:
expect([0,1,2,3,4,5,6,7,8,9], 'to contain', [0,1,3,4,5,6,7,8,9]) UnexpectedError: expected [ 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 ] to contain [ 0, 1, 3, 4, 5, 6, 7, 8, 9 ] Did not contain: 2
The text was updated successfully, but these errors were encountered:
to contain takes varargs, not an array of items that the subject array must contain. The first example should probably have looked like this:
to contain
> expect([0, 1, 3, 4, 5, 6, 7, 8, 9], 'to contain', 0, 1, 2, 3, 4, 5, 6, 7, 8, 9) UnexpectedError: expected [ 0, 1, 3, 4, 5, 6, 7, 8, 9 ] to contain 0, 1, 2, 3, 4, 5, 6, 7, 8, 9
I think this feature req is a great idea. It should be relatively easy, so it might even work as a good "first PR".
Sorry, something went wrong.
@papandreou you are right that we shouldn't output the arguments as an array either.
@sunesimonsen @papandreou I tried to make PR for this, but it already seems make output when I ran it like below:
(same as papandreou said)
Is it already resolved? I am wondering if this issue is valid until now. :-)
No branches or pull requests
This is out current output:
It would be better if we did the following:
The text was updated successfully, but these errors were encountered: