mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-17 04:24:35 +03:00
a40bf10b9f
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.
29 lines
1.3 KiB
Markdown
29 lines
1.3 KiB
Markdown
## Running tests
|
|
|
|
```bash
|
|
pip install -r requirements.txt
|
|
pytest --hge-urls "http://127.0.0.1:8080" --pg-urls "postgresql://admin@127.0.0.1:5432/hge_tests" -vv
|
|
```
|
|
|
|
## Tests Structure
|
|
|
|
- Tests are grouped as test classes in test modules (names starting with `test_`)
|
|
|
|
- The configuration files (if needed) for the tests in a class are usually kept in one folder.
|
|
- The folder name is usually either the `dir` variable or the `dir()` function
|
|
|
|
|
|
- Some tests (like in `test_graphql_queries.py`) requires a setup and teardown per class.
|
|
- Here we are extending the `DefaultTestSelectQueries` class.
|
|
- This class defines a fixture which will run the configurations in `setup.yaml` and `teardown.yaml` once per class
|
|
- Extending test class should define a function name `dir()`, which returns the configuration folder
|
|
|
|
|
|
- For mutation tests (like in `test_graphql_mutations.py`)
|
|
- We need a `schema_setup` and `schema_teardown` per class
|
|
- And `values_setup` and `values_teardown` per test
|
|
- Doing schema setup and teardown per test is expensive.
|
|
- We are extending the `DefaultTestMutations` class for this.
|
|
- This class defines a fixture which will run the configuration in `setup.yaml` and `teardown.yaml` once per class.
|
|
- Another fixture defined in this class runs the configuration in `values_setup.yaml` and `values_teardown.yaml` once per class.
|