Extend JToken assertions

ronaldkroon commented 7 years ago

Add the following JToken assertions:

NotHaveValue (opposite of existing HaveValue)
NotHaveElement (opposite of existing HaveElement)
ContainSingleItem (allows to do extra assertions on the found item)
HaveCount
Equal / NotEqual (accept a JSON string as expectation)

dennisdoomen commented 6 years ago

Is this still relevant? If so, please rebase on release-5.0.0

ronaldkroon commented 6 years ago

Only the last commit is still relevant (rest already merged). I want to add a method that takes a string in JSON format to compare with. But then we have:

Be
BeEquivalent
Equal (new in this PR) And the opposites. The first two behave the similar, but the second one has more sophisticated error messages. In this PR I added another one because a string gets implicitly converted to a JValue which is different than a parsed JSON string. Be will use the JValue, BeEquivalent will throw because it doesn't understand the string, Equal will use the parsed JSON.

We need to decide what to do with this.

BTW: NotBeEquivalent does not behave exactly as the opposite of BeEquivalent.

I can work on this when the plan is clear.

dennisdoomen commented 6 years ago

So if we can get some breaking changes in, what would we want to keep?

fluentassertions / fluentassertions.json

Extend JToken assertions #4