Open hsq125 opened 3 years ago
This is partially the reason I'm switching to using jsonschema in the next release, it should be able to provide more useful errors like
../../.tox/py38-generic/lib/python3.8/site-packages/tavern/_core/schema/jsonschema.py:134: in verify_jsonschema
raise BadSchemaError(msg) from e
E tavern._core.exceptions.BadSchemaError:
E ---
E
E Additional properties are not allowed ('blllblbb' was unexpected)
E
E - name: Send with basic auth
E blllblbb: gg
E request:
E url: "{global_host}/authtest/basic"
E method: GET
E auth:
E - "fakeuser"
E - "fakepass"
E response:
E status_code: 200
E json:
E auth_type: basic
E auth_user: fakeuser
E auth_pass: fakepass
For the time being you can also use the pytest -q
flag which won't print so many lines of code in each traceback
I'm stuck for hours with a simple test with one config file and one external stage file.
Each time there is a single mistake, I'm left with a stack trace of 500 line without clear indication about what is wrong.
This is just an example, but Tavern crashes here and there depending on the issue. That is not possible to use this in a productive way.