graphql-engine

hasura/graphql-engine

Fork 0

mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-14 17:02:49 +03:00

Commit Graph

Author	SHA1	Message	Date
Samir Talwar	7c452bfca1	server/tests-py: Spawn a new PostgreSQL schema ("database") per test. When running using the "new" style (with a HGE binary, not a URL), a new PostgreSQL metadata and source database are created for each test. When we get this into CI, this should drastically reduce the flakiness. I have also enabled parallelization by default when using `run-new.sh`. It's much faster. I had to basically rewrite _server/tests-py/test_graphql_read_only_source.py_ so that it does two different things depending on how it's run. It's unfortunate, but it should eventually go away. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/6879 GitOrigin-RevId: a121b9035f8da3e61a3e36d8b1fbc6ccae918fad	2022-11-15 19:08:53 +00:00
Samir Talwar	5df8419a4f	server/tests-py: Use markers for backends instead of parameterized tests. I'm trying to shore up the Python integration tests to make them more reliable. In doing so, I noticed this. --- It feels a lot more sensible as we never run on more than one backend at a time. This also removes the `check_file_exists` parameter from the setup functions; it never worked. It was always set to the result of a comparison between a backend name and a function, which was always `False`. Enabling it breaks things. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5254 GitOrigin-RevId: 8718ab21527c2ba0a7205d1c01ebaac1a10be844	2022-08-02 19:33:59 +00:00
Anon Ray	e87433c2bb	server: remove hdb_lib and add tests for read-only source PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3634 Co-authored-by: Philip Lykke Carlsen <358550+plcplc@users.noreply.github.com> GitOrigin-RevId: 2db62a279496cd7e5dd57bdf02c3efa7b70042c8	2022-02-21 10:00:00 +00:00

Author

SHA1

Message

Date

Samir Talwar

7c452bfca1

server/tests-py: Spawn a new PostgreSQL schema ("database") per test.

When running using the "new" style (with a HGE binary, not a URL), a new PostgreSQL metadata and source database are created for each test. When we get this into CI, this should drastically reduce the flakiness.

I have also enabled parallelization by default when using `run-new.sh`. It's much faster.

I had to basically rewrite _server/tests-py/test_graphql_read_only_source.py_ so that it does two different things depending on how it's run. It's unfortunate, but it should eventually go away.

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/6879
GitOrigin-RevId: a121b9035f8da3e61a3e36d8b1fbc6ccae918fad

2022-11-15 19:08:53 +00:00

Samir Talwar

5df8419a4f

server/tests-py: Use markers for backends instead of parameterized tests.

I'm trying to shore up the Python integration tests to make them more reliable. In doing so, I noticed this.

---

It feels a lot more sensible as we never run on more than one backend at a time.

This also removes the `check_file_exists` parameter from the setup functions; it never worked. It was always set to the result of a comparison between a backend name and a function, which was always `False`. Enabling it breaks things.

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5254
GitOrigin-RevId: 8718ab21527c2ba0a7205d1c01ebaac1a10be844

2022-08-02 19:33:59 +00:00

Anon Ray

e87433c2bb

server: remove hdb_lib and add tests for read-only source

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3634
Co-authored-by: Philip Lykke Carlsen <358550+plcplc@users.noreply.github.com>
GitOrigin-RevId: 2db62a279496cd7e5dd57bdf02c3efa7b70042c8

2022-02-21 10:00:00 +00:00

3 Commits