graphql-engine/server/tests-py/queries/graphql_mutation/update/basic/schema_teardown.yaml

type: bulk
args:
#Drop relationship first
- type: drop_relationship
  args:
    table:
      name: author
      schema: public
    relationship: articles

- type: run_sql
  args:
    sql: |
      drop table article

- type: run_sql
  args:
    sql: |
      drop table author

- type: run_sql
  args:
    sql: |
      drop table person

- type: run_sql
  args:
    sql: |
      drop table numerics
python based tests (#387) 2018-09-18 09:21:57 +03:00			`type: bulk`
			`args:`
			`#Drop relationship first`
			`- type: drop_relationship`
			`args:`
run graphql tests on both http and websocket; add parallelism (close #1868) (#1921) Examples 1) ` pytest --hge-urls "http://127.0.0.1:8080" --pg-urls "postgresql://admin@127.0.0.1:5432/hge_tests" -vv ` 2) `pytest --hge-urls "http://127.0.0.1:8080" "http://127.0.0.1:8081" --pg-urls "postgresql://admin@127.0.0.1:5432/hge_tests" "postgresql://admin@127.0.0.1:5432/hge_tests2" -vv ` ### Solution and Design <!-- How is this issue solved/fixed? What is the design? --> <!-- It's better if we elaborate --> #### Reducing execution time of tests - The Schema setup and teardown, which were earlier done per test method, usually takes around 1 sec. - For mutations, the model has now been changed to only do schema setup and teardown once per test class. - A data setup and teardown will be done once per test instead (usually takes ~10ms). - For the test class to get this behaviour, one can can extend the class `DefaultTestMutations`. - The function `dir()` should be define which returns the location of the configuration folder. - Inside the configuration folder, there should be - Files `<conf_dir>/schema_setup.yaml` and `<conf_dir>/schema_teardown.yaml`, which has the metadata query executed during schema setup and teardown respectively - Files named `<conf_dir>/values_setup.yaml` and `<conf_dir>/values_teardown.yaml`. These files are executed to setup and remove data from the tables respectively. #### Running Graphql queries on both http and websockets - Each GraphQL query/mutation is run on the both HTTP and websocket protocols - Pytests test parameterisation is used to achieve this - The errors over websockets are slightly different from that on HTTP - The code takes care of converting the errors in HTTP to errors in websockets #### Parallel executation of tests. - The plugin pytest-xdist helps in running tests on parallel workers. - We are using this plugin to group tests by file and run on different workers. - Parallel test worker processes operate on separate postgres databases(and separate graphql-engines connected to these databases). Thus tests on one worker will not affect the tests on the other worker. - With two workers, this decreases execution times by half, as the tests on event triggers usually takes a long time, but does not consume much CPU. 2019-04-08 10:22:38 +03:00			`table:`
python based tests (#387) 2018-09-18 09:21:57 +03:00			`name: author`
			`schema: public`
			`relationship: articles`

			`- type: run_sql`
			`args:`
			`sql: \|`
			`drop table article`

			`- type: run_sql`
			`args:`
			`sql: \|`
			`drop table author`

			`- type: run_sql`
			`args:`
			`sql: \|`
			`drop table person`
server: _inc for non-integer numeric types (fix #3573) (#4429) * Allow `_inc` to update other numeric types in addition to integers * Add support for PostgreSQL's `money` field type * Add support for _inc on money types * Add note of generalized `_inc` support to changelog 2020-04-17 12:32:09 +03:00
			`- type: run_sql`
			`args:`
			`sql: \|`
			`drop table numerics`