Rakesh Emmadi
|
b844c5d732
|
server/tests: unify HASURA_BIGQUERY_SERVICE_KEY and HASURA_BIGQUERY_SERVICE_ACCOUNT env vars
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3914
GitOrigin-RevId: 66f75420504d1b864b91599c2bdaa832784bb956
|
2022-03-14 07:50:35 +00:00 |
|
Abby Sassel
|
a091110364
|
server/tests: ephemeral BigQuery projects for CI test jobs
_Problem_
We currently run teardown/`DELETE` statements on the same, shared `hasura_test` dataset. This is not ideal as parallel test runs can and do affect each other, resulting in nondeterministic CI failures.
Closes https://github.com/hasura/graphql-engine-mono/issues/2521
_Solution and design_
This PR introduces ephemeral, isolated projects for each test run _in CI only_. Projects are created within [the Google Cloud Platform `data-sources-test-bigquery` directory](https://console.cloud.google.com/iam-admin/settings?folder=704256416468&orgonly=true&supportedpurview=organizationId) on each test run, and destroyed afterwards.
I've only introduced this change in CI for the time being:
1. this isn't as much of an issue locally because we're less likely to run bigquery tests in parallel.
2. to more quickly unblock https://github.com/hasura/graphql-engine/issues/7929.
3. to limit the number of new projects created until we have a better idea of our usage vs GCP quota/limits.
Also updated the [internal wiki here](https://github.com/hasura/graphql-engine-mono/wiki/Testing-BigQuery) with this info.
_To verify_
- CI: [this job](https://buildkite.com/hasura/graphql-engine-mono/builds/3770#89e5bac6-16fe-447e-bcda-85cd47ea1b77) successfully runs all tests on a temporary project & dataset
- local: follow [these steps](https://github.com/hasura/graphql-engine-mono/wiki/Testing-BigQuery#ci--optional-dedicated-gcp-project-for-tests) to try the same setup locally
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3240
GitOrigin-RevId: d88d9cb7922266bfa962cfcb481e0272b8929a5d
|
2022-01-25 08:28:06 +00:00 |
|
Abby Sassel
|
6b3db83737
|
server/bigquery: run tests in CI
server/bigquery: run tests in CI #1525
[Example of successful BigQuery test job](https://app.circleci.com/pipelines/github/hasura/graphql-engine-mono/15951/workflows/86deb614-ddbc-4df5-9af3-288eeff6504a/jobs/283568)
TODO:
- [ ] I'll make corresponding changes in the OSS repo once this is merged
- [ ] @scriptnull or anyone with permissions: to require in CI
https://github.com/hasura/graphql-engine-mono/pull/1741
GitOrigin-RevId: d4ba446e9b13d213de135c73bb72973478575a29
|
2021-08-12 16:48:29 +00:00 |
|
Abby Sassel
|
1cd9fc376d
|
server/mysql: integrate MySQL tests into dev.sh workflow
https://github.com/hasura/graphql-engine-mono/pull/1848
GitOrigin-RevId: 2bd7c0a18448f042a1e35d21aaf42232acf48a46
|
2021-07-21 17:22:56 +00:00 |
|
Abby Sassel
|
76c322589c
|
server/bigquery: Document BigQuery integration tests
This PR documents & streamlines how we run BigQuery integration tests locally as a first step to [running them in CI](https://github.com/hasura/graphql-engine-mono/issues/1525).
I've also created a hasura service account for internal use. [Internal docs here](https://github.com/hasura/graphql-engine-mono/wiki/Testing-BigQuery).
Thanks to FP Complete team for [the guidance here](https://docs.google.com/document/d/1dGDK0touUtsDxRQPonMxSoPbIfzBoSYo02tAjQEO7qA/edit?ts=60c0cf24#), which I've reused parts of.
https://github.com/hasura/graphql-engine-mono/pull/1732
GitOrigin-RevId: 303819d212aa073fbef685d077b1cfa583cd15fc
|
2021-07-06 11:13:06 +00:00 |
|
Abby Sassel
|
dc950eda6a
|
server/test: fix BACKEND variable in dev.sh script
GitOrigin-RevId: 0dae37c0aa50c8e4be59618d9d0a777f537fa4dc
|
2021-06-09 09:51:07 +00:00 |
|
Abby Sassel
|
41908936cf
|
server: improve backend-specific test setup
GitOrigin-RevId: c40393bcdd78feaba7e9490ce4ed78de19b5bfc5
|
2021-05-25 13:55:11 +00:00 |
|