graphql-engine/server/tests-py/test_schema_duplication.py
Samir Talwar 8cb2738cbe server/tests-py: Declaratively state the HGE environment variables.
This has two purposes:

* When running the Python integration tests against a running HGE instance, with `--hge-url`, it will check the environment variables available and actively skip the test if they aren't set. This replaces the previous ad-hoc skip behavior.
* More interestingly, when running against a binary with `--hge-bin`, the environment variables are passed through, which means different tests can run with different environment variables.

  On top of this, the various services we use for testing now also provide their own environment variables, rather than expecting a test script to do it.

In order to make this work, I also had to invert the dependency between various services and `hge_ctx`. I extracted a `pg_version` fixture to provide the PostgreSQL version, and now pass the `hge_url` and `hge_key` explicitly to `ActionsWebhookServer`.

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/6028
GitOrigin-RevId: 16d866741dba5887da1adf4e1ade8182ccc9d344
2022-09-28 09:21:02 +00:00

22 lines
758 B
Python

#!/usrbin/env python3
import pytest
from validate import check_query_f
@pytest.mark.usefixtures('actions_fixture', 'per_method_tests_db_state')
class TestSchemaDuplication:
@classmethod
def dir(cls):
return "queries/schema/duplication/"
def test_create_action_followed_by_track_table(self, hge_ctx):
check_query_f(hge_ctx, self.dir() + "create_action_and_track_table_fail.yaml")
def test_track_table_followed_by_create_action(self, hge_ctx):
check_query_f(hge_ctx, self.dir() + "track_table_and_create_action_fail.yaml")
def test_track_table_with_conflicting_custom_root_node_names(self, hge_ctx):
check_query_f(hge_ctx, self.dir() + 'track_table_with_conflicting_custom_root_node_names_fail.yaml')