Open
Conversation
ex. use testData.expectError where possible
previously, since the test data was generated as it wrote to the database, different timings of the database writes could generate different data. this generates all the data first, and then writes that data. i also separated the data logging -- which cleans up the code slightly -- the command line make fake data can log without having to worry about the tests generating logs ( and mucking up the test output )
probably from a global find and replace from the command line parameters lookup
Contributor
Author
|
adds a custom "test runner" so that we can specify command line parameters to run specific tests. misc:
|
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.
minor changes to the test data generation
( part of improving things for potentially changing the table format )