hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-16 18:42:30 +03:00
Code Issues Projects Releases Wiki Activity
17c3d25b1b
graphql-engine/server/tests-py/requirements-top-level.txt

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

21 lines
521 B
Plaintext
Raw Normal View History

server: Use `make` to simplify tests-py venv generation. Rather than a homebrewed approach, we can use `make` to figure out when it's necessary to regenerate our venv. This Makefile will regenerate _requirements.txt_ from _requirements-top-level.txt_ when the latter is changed. It will also regenerate the venv when _requirements.txt_ is changed (i.e. changes are pulled, or it's regenerated as described above). `make` uses file/directory timestamps to figure out what to rebuild. This is probably more reliable than expecting people to update a version number whenever they change a file. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5152 GitOrigin-RevId: 24b27d49bf6c4ba1d57ac38ea38ae278216c6d66
2022-07-25 23:03:57 +03:00
# Direct dependencies go here.
server/tests-py: Install the `pytest-durations` plugin. [pytest-durations][] is an enhancement to pytest over the built-in [`--durations` parameter][] which also shows the duration of setup, teardown, and fixtures that take the longest. While it's not strictly necessary now, I used it to figure out what was taking so long when trying to run things in parallel, and found it very helpful, so I think it's worth preserving. [pytest-durations]: https://pypi.org/project/pytest-durations/ [`--durations` parameter]: https://docs.pytest.org/en/6.2.x/usage.html#profiling-test-execution-duration PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5480 GitOrigin-RevId: b789418dd4c971adb91e08b7837a962bede44452
2022-08-15 19:14:23 +03:00
# Regenerate requirements.txt by running `make server/tests-py/requirements.txt`.
server: Use `make` to simplify tests-py venv generation. Rather than a homebrewed approach, we can use `make` to figure out when it's necessary to regenerate our venv. This Makefile will regenerate _requirements.txt_ from _requirements-top-level.txt_ when the latter is changed. It will also regenerate the venv when _requirements.txt_ is changed (i.e. changes are pulled, or it's regenerated as described above). `make` uses file/directory timestamps to figure out what to rebuild. This is probably more reliable than expecting people to update a version number whenever they change a file. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5152 GitOrigin-RevId: 24b27d49bf6c4ba1d57ac38ea38ae278216c6d66
2022-07-25 23:03:57 +03:00
server: Re-freeze tests-py/requirements.txt. I tried re-freezing _server/tests-py/requirements-top-level.txt_ recently, and discovered that it caused the tests to fail. This pins a couple of dependencies so that we can safely re-freeze. Specifically: - `cryptography` is pinned at v3.* - `graphene` is pinned at v2.* - `PyJWT` is pinned at v2.3.* - `websocket-client` is pinned at v0.56.0 (this was done in _requirements.txt_ already, but that file is supposed to be regenerated) Upgrading `SQLAlchemy` required changing PostgreSQL URLs to use "postgresql://" as the URL scheme, not "postgres://". Updating `ruamel.yaml` caused a few tests to fail as we are passing `ruamel.yaml.scalarstring.LiteralScalarString` values as header values. This is fixed by explicitly converting header values to strings. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5120 GitOrigin-RevId: 9c12a3013c3d1f23dddbe781037663838b23f6f5
2022-07-22 13:24:24 +03:00
croniter
cryptography == 3.* # later versions require Rust support
graphene == 2.* # v3 has changed the API
graphql-core
jsondiff
freeze requirements.txt for server tests (#2450)
2019-07-01 16:34:48 +03:00
psycopg2-binary
server: Re-freeze tests-py/requirements.txt. I tried re-freezing _server/tests-py/requirements-top-level.txt_ recently, and discovered that it caused the tests to fail. This pins a couple of dependencies so that we can safely re-freeze. Specifically: - `cryptography` is pinned at v3.* - `graphene` is pinned at v2.* - `PyJWT` is pinned at v2.3.* - `websocket-client` is pinned at v0.56.0 (this was done in _requirements.txt_ already, but that file is supposed to be regenerated) Upgrading `SQLAlchemy` required changing PostgreSQL URLs to use "postgresql://" as the URL scheme, not "postgres://". Updating `ruamel.yaml` caused a few tests to fail as we are passing `ruamel.yaml.scalarstring.LiteralScalarString` values as header values. This is fixed by explicitly converting header values to strings. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5120 GitOrigin-RevId: 9c12a3013c3d1f23dddbe781037663838b23f6f5
2022-07-22 13:24:24 +03:00
PyJWT == 2.3.* # v2.4 disallows the key format we use
pytest == 6.2.5
server/tests-py: Install the `pytest-durations` plugin. [pytest-durations][] is an enhancement to pytest over the built-in [`--durations` parameter][] which also shows the duration of setup, teardown, and fixtures that take the longest. While it's not strictly necessary now, I used it to figure out what was taking so long when trying to run things in parallel, and found it very helpful, so I think it's worth preserving. [pytest-durations]: https://pypi.org/project/pytest-durations/ [`--durations` parameter]: https://docs.pytest.org/en/6.2.x/usage.html#profiling-test-execution-duration PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5480 GitOrigin-RevId: b789418dd4c971adb91e08b7837a962bede44452
2022-08-15 19:14:23 +03:00
pytest-durations
server/tests-py: Make HGECtxGQLServer a fixture. Starting it and stopping it for the various tests that actually use it. There are only a few. This also removes some dead code and fixes warnings in _test_webhook_request_context.py_. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5846 GitOrigin-RevId: 7760467f9de7b1f9718e7482275c298eeaa3ad3a
2022-09-15 00:41:28 +03:00
pytest-fixture-order
freeze requirements.txt for server tests (#2450)
2019-07-01 16:34:48 +03:00
pytest-xdist
server: Re-freeze tests-py/requirements.txt. I tried re-freezing _server/tests-py/requirements-top-level.txt_ recently, and discovered that it caused the tests to fail. This pins a couple of dependencies so that we can safely re-freeze. Specifically: - `cryptography` is pinned at v3.* - `graphene` is pinned at v2.* - `PyJWT` is pinned at v2.3.* - `websocket-client` is pinned at v0.56.0 (this was done in _requirements.txt_ already, but that file is supposed to be regenerated) Upgrading `SQLAlchemy` required changing PostgreSQL URLs to use "postgresql://" as the URL scheme, not "postgres://". Updating `ruamel.yaml` caused a few tests to fail as we are passing `ruamel.yaml.scalarstring.LiteralScalarString` values as header values. This is fixed by explicitly converting header values to strings. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5120 GitOrigin-RevId: 9c12a3013c3d1f23dddbe781037663838b23f6f5
2022-07-22 13:24:24 +03:00
PyYAML
Add a new /dev/rts_stats endpoint, enabled when '+RTS -T' GitOrigin-RevId: e347bc2f66bad814516662e34bbd8322c214be25
2021-04-13 20:32:29 +03:00
redis
server: Re-freeze tests-py/requirements.txt. I tried re-freezing _server/tests-py/requirements-top-level.txt_ recently, and discovered that it caused the tests to fail. This pins a couple of dependencies so that we can safely re-freeze. Specifically: - `cryptography` is pinned at v3.* - `graphene` is pinned at v2.* - `PyJWT` is pinned at v2.3.* - `websocket-client` is pinned at v0.56.0 (this was done in _requirements.txt_ already, but that file is supposed to be regenerated) Upgrading `SQLAlchemy` required changing PostgreSQL URLs to use "postgresql://" as the URL scheme, not "postgres://". Updating `ruamel.yaml` caused a few tests to fail as we are passing `ruamel.yaml.scalarstring.LiteralScalarString` values as header values. This is fixed by explicitly converting header values to strings. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5120 GitOrigin-RevId: 9c12a3013c3d1f23dddbe781037663838b23f6f5
2022-07-22 13:24:24 +03:00
requests
ruamel.yaml
sqlalchemy
websocket-client == 0.56.0 # 0.58.0 and above changed the function signatures of callbacks
Reference in New Issue Copy Permalink