feat: implement AxeResult.ToString based on JsonConvert #75
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Details
This PR adds in a basic ToString implementation for
AxeResult
andAxeResultItem
that just usesJsonConvert.SerializeObject
.The motivation for this is that these types are likely to be used in users' test assertions; when an assertion related to them fails, we want the test output to be actionable.
I wanted to reuse the same
JsonSerializerSettings
as everywhere else in the Selenium package, so I extracted it out ofAxeBuilder
(and several tests that repeated bits of it) into aAxeJsonSerializerSettings
static class in the commons package. I think this is a better home for the serializer settings anyway, since they're tightly coupled to the implementation of the types.The test addition will have a merge conflict to resolve with #74, which adds overlapping unit tests that share the same sample input JSON.
Example output of
AxeResult.ToString()
using the pinned sample input from the new unit test: