graphql-engine/server/tests-py/queries/graphql_mutation/insert/onconflict/values_setup.yaml

type: bulk
args:

#Insert Author table data
- type: insert
  args:
    table: author
    objects:
      - name: Author 1
      - name: Author 2

#Insert aticle table data
- type: insert
  args:
    table: article
    objects:
    - content: Sample article content
      title: Article 1
    - content: Sample article content
      title: Article 2
    - content: Sample article content
      title: Article 3

#Insert into orders
- type: insert
  args:
    table: orders
    objects:
    - placed: '2017-08-19 14:22:11.802755+02'
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			`type: bulk`
			`args:`

			`#Insert Author table data`
			`- type: insert`
			`args:`
			`table: author`
			`objects:`
			`- name: Author 1`
			`- name: Author 2`

			`#Insert aticle table data`
			`- type: insert`
			`args:`
			`table: article`
			`objects:`
			`- content: Sample article content`
			`title: Article 1`
			`- content: Sample article content`
			`title: Article 2`
			`- content: Sample article content`
			`title: Article 3`

support where clause in on_conflict of insert mutation (close #2795) (#3002) 2019-10-09 13:09:20 +03:00			`#Insert into orders`
			`- type: insert`
			`args:`
			`table: orders`
			`objects:`
			`- placed: '2017-08-19 14:22:11.802755+02'`