Test validators on each levels of schema

[kloud-byun]

• test_inputfield_validation.py

  • test_valid
  • test_invalid
  • test_list_validate_item
  • test_list_mixed_valid
    • actually kept this since the operated input will be different than the one for argument level
  • test_nested_invalid
    • tested input field of input field (nested)

• test_inputobject_validation.py

  • tested validation on a simple relationship between "profession" and "hobbies"
  • test_valid_user
  • test_no_profession_provided
  • test_invalid_profession_given_hobbies
  • test_invalid_profession_name
  • test_invalid_multiple_errors

  Added in static type check assertions for test cases along with # type: ignore[list-item] for the list validator.

[kloud-byun]

Kept both test_inputobject_validation.py and test_inputfield_validation.py as simple as possible; to simply test the validity of the validators at each levels of the schema.
InputField validations will test for each single InputField individually, while InputObject validations will test for validity of collection of InputFields.

[kloud-byun]

• test_field_validation.py
  • test_valid_user
  • test_valid_no_profession
  • test_invalid_profession_given_hobbies
  • test_invalid_profession_starts_with_username
  • test_invalid_multiple_errors

Finished the test_field_validation.py as well. Currently mirrors the same tests from test_inputobject_validation.py, but it just applies the validator at the Field level rather than at the InputObject level.

That finishes the validation testings at all 4 different levels of the schema. Test scripts for Field and InputObject are pretty much equivalent, except the targeted level; and test scripts for Argument and InputField are very similar as well, except Argument test file is the only test file that consists of 4 extra GraphQL validations.

If required, I can also include the generic GraphQL validation test cases for the rest 3 of the test files.
I tried to mirror the test cases to keep the consistency between the files, since most of the complex and unique validators + nested validators will be tested within test_complex_validation.py. But I can add/modify the test cases so that none of the test files will be redundant or similar to each other - if required.

Working on test_validators.py that will simply test to cover all the branches of validators.py, then I'll move on to test_complex_validation.py.

[kloud-byun]

When raising assertions for the validators at Field and InputObject level, the errors are being stored in result.errors[0].extensions[''] for Field and result.errors[0].extensions['input'][0][''] for InputObject. I can modify the path to be something else by adding an additional layer within the validator function, but wasn't sure if that was desired.
Also, test_validators.py now utilizes fixture & parametrize to keep the file simple and clean.