External data plugin, support for JSON files #2700
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 11 commits
March 21, 2023 17:09
…ndata. Added support for nested arrays of objects.
…ctively used in ExternalDataFromJson.feature (price)
…data documentation
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The PR extends the External Data Plugin to support JSON files, analogous to added support for excel/csv in #2429.
Code for handling the json is heavily based on https://github.com/kazantsev033/SpecFlow.Contrib.JsonData by @kazantsev033, but support was added for nested arrays of json objects.
The new concept is demonstrated by the /Plugins/SpecFlow.ExternalData/sample/ExternalDataSample/Features/ExternalDataFromJson.feature file.
Checklist:
I've added tests for my code. (most of the time mandatory)
I have added an entry to the changelog. (mandatory)
My change requires a change to the documentation.
I have updated the documentation accordingly.