graphql-engine/server/tests-py/requirements-top-level.txt

psycopg2-binary
sqlalchemy
pytest==4.5.0
pytest-xdist
requests
pyyaml
websocket-client
pyjwt >= 1.5.3
jsondiff
cryptography
graphene
brotlipy
ruamel.yaml > 0.15
graphql-core
freeze requirements.txt for server tests (#2450) 2019-07-01 16:34:48 +03:00			`psycopg2-binary`
			`sqlalchemy`
In tests/dev.sh: upgrade ruamel to support python 3.7. Closes #3312 Tested on python 3.5 and 3.7 We make light use of pyenv to set an appropriate python version if installed. We could easily install a correct version too if we wanted but that seemed invasive. The newer ruamel was an annoying upgrade but also offers some improvements that exposed some test suite issues (fixed later). 2019-11-14 19:32:11 +03:00			`pytest==4.5.0`
freeze requirements.txt for server tests (#2450) 2019-07-01 16:34:48 +03:00			`pytest-xdist`
			`requests`
			`pyyaml`
			`websocket-client`
			`pyjwt >= 1.5.3`
			`jsondiff`
			`cryptography`
			`graphene`
add gzip brotli compression to http responses (close #2674) (#2751) 2019-09-19 15:54:40 +03:00			`brotlipy`
In tests/dev.sh: upgrade ruamel to support python 3.7. Closes #3312 Tested on python 3.5 and 3.7 We make light use of pyenv to set an appropriate python version if installed. We could easily install a correct version too if we wanted but that seemed invasive. The newer ruamel was an annoying upgrade but also offers some improvements that exposed some test suite issues (fixed later). 2019-11-14 19:32:11 +03:00			`ruamel.yaml > 0.15`
Test result ordering, add `--accept` test mode to automatically accept changed test cases We add a new pytest flag `--accept` that will automatically write back yaml files with updated responses. This makes it much easier and less error-prone to update test cases when we expect output to change, or when authoring new tests. Second we make sure to test that we actually preserve the order of the selection set when returning results. This is a "SHOULD" part of the spec but seems pretty important and something that users will rely on. To support both of the above we use ruamel.yaml which preserves a certain amount of formatting and comments (so that --accept can work in a failry ergonomic way), as well as ordering (so that when we write yaml the order of keys has meaning that's preserved during parsing). Use ruamel.yaml everywhere for consistency (since both libraries have different quirks). Quirks of ruamel.yaml: - trailing whitespace in multiline strings in yaml files isn't written back out as we'd like: https://bitbucket.org/ruamel/yaml/issues/47/multiline-strings-being-changed-if-they - formatting is only sort of preserved; ruamel e.g. normalizes indentation. Normally the diff is pretty clean though, and you can always just check in portions of your test file after --accept fixup 2019-09-04 18:02:35 +03:00			`graphql-core`