budibase/qa-core
Rory Powell 77ffb8d86d Run integration suite in CI again / auto detect tenancy / refactors (#10209)
* qa-core-ci-fixes

* global setup and teardown wip

* Updates to logs and setup

* Remove date and console mocking

* Update CI to spin up minimal dev env

* Update readme

* Fix scopeBackend.sh

* Ensure docker services are initialised before starting worker

* Lint

* Fix admin user being created on startup (#10219)

* use regular bootstrap and build

* Lint

* Temp: re-use global setup to get around app limit in QA
2023-04-05 15:33:56 +01:00
..
scripts Run integration suite in CI again / auto detect tenancy / refactors (#10209) 2023-04-05 15:33:56 +01:00
src Run integration suite in CI again / auto detect tenancy / refactors (#10209) 2023-04-05 15:33:56 +01:00
.gitignore Run integration suite in CI again / auto detect tenancy / refactors (#10209) 2023-04-05 15:33:56 +01:00
README.md Run integration suite in CI again / auto detect tenancy / refactors (#10209) 2023-04-05 15:33:56 +01:00
jest.config.ts Run integration suite in CI again / auto detect tenancy / refactors (#10209) 2023-04-05 15:33:56 +01:00
package.json Run integration suite in CI again / auto detect tenancy / refactors (#10209) 2023-04-05 15:33:56 +01:00
tsconfig.json QA Core tests for app creation 2022-10-01 02:54:51 +01:00
yarn.lock Run integration suite in CI again / auto detect tenancy / refactors (#10209) 2023-04-05 15:33:56 +01:00

README.md

QA Core API Tests

The QA Core API tests are a jest suite that run directly against the budibase backend APIs.

Auto Setup

You can run the whole test suite with one command, that spins up the budibase server and runs the jest tests:

yarn test:ci

Setup Server

You can run the local development stack by following the instructions on the main readme.

Run Tests

If you configured the server using the previous command, you can run the whole test suite by using:

yarn test

for watch mode, where the tests will run on every change:

yarn test:watch

To run tests locally against a cloud service you can update the configuration inside the .env file and run:

yarn test