Implement isPrimaryKey check, fix and refactor check tests #250
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.
Issue #, if available:
#249
Description of changes:
isPrimaryKeycheck implementation.tests/test_checks.pyare fixed and refactored as follows:pytest.mark.xfailmarks are removed (according to pytest docs they are meant for cases when feature is not yet implemented or there is a new bug which cannot be fixed yet; also with such marks on tests with multiple asserts it is not obvious which asserts are supposed to fail);"Success"and"Failure"checks are rearranged so that the former are grouped intest_<check>and the latter - intest_fail_<check>methods;run_checkhelper to simplify check tests;By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.