graphql-engine/server/tests-py/queries/v1/select/basic
nizar-m 0ffb0478b9 Tests for server with access control, and some more tests (#710)
* 1) Tests for creating permissions
2) Test for constraint_on with GraphQL insert on_conflict

* Run tests with access key and webhook

* Tests for GraphQL query with quoted columns

* Rewrite test-server.sh so that it can be run locally

* JWT based tests

* Tests with various postgres types

* For tests on select queries, run setup only once per class

* Tests for v1 count queries

* Skip teardown for tests that does not modify data

* Workaround for hpc 'parse error when reading .tix file'

* Move GeoJson tests to the new structure

* Basic tests for v1 queries

* Tests for column, table or operator not found error cases on GraphQL queries

* Skip test teardown for mutation tests which does not change database state, even when it returns 200.
2018-10-28 23:57:49 +05:30
..
nested_select_query_article_author_rel_alias.yaml Tests for server with access control, and some more tests (#710) 2018-10-28 23:57:49 +05:30
nested_select_query_article_author.yaml add python based tests, remove haskell tests 2018-10-04 18:14:15 +05:30
nested_select_where_query_author_article.yaml add python based tests, remove haskell tests 2018-10-04 18:14:15 +05:30
select_article_col_not_present_err.yaml python based tests (#387) 2018-09-18 11:51:57 +05:30
select_article_table_not_present_err.yaml Tests for server with access control, and some more tests (#710) 2018-10-28 23:57:49 +05:30
select_article.yaml python based tests (#387) 2018-09-18 11:51:57 +05:30
select_query_author_where.yaml add python based tests, remove haskell tests 2018-10-04 18:14:15 +05:30
select_user.yaml breaking: encode bigint and bigserial postgres types as strings in response (fix #633) (#640) 2018-10-05 10:46:21 +05:30
setup.yaml breaking: encode bigint and bigserial postgres types as strings in response (fix #633) (#640) 2018-10-05 10:46:21 +05:30
teardown.yaml breaking: encode bigint and bigserial postgres types as strings in response (fix #633) (#640) 2018-10-05 10:46:21 +05:30