Tests for SchemaParser class - #22
Open
siboxd wants to merge 22 commits into
Open
Conversation
…ts the xsd read file) You had to change the newParseContext to adhere what "xsd" dictates
…ource classes need to be updated as well
- Implemented VastXsdSchemaParserTest
…t code; Vast tests passing
…t code; Vast tests passing
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I've added automated tests for SchemaParser class that will generate some classes and compere them with the pre-generated classes inside the project, to test whether the generation was successful.
Any change to generation engine should reflect in a change of those resource files to let tests pass again.
#20 and #21 are already inside that code, because otherwise it wouldn't have worked