2022-09-02 13:18:23 -06:00
# Integration tests
2018-01-27 11:52:41 -07:00
2018-01-08 09:29:52 -07:00
Integration tests can be run with make commands for the
appropriate backends, namely:
2018-10-14 22:13:21 -06:00
```shell
make test-sqlite
2022-09-02 13:18:23 -06:00
make test-pgsql
make test-mysql
make test-mssql
2018-10-14 22:13:21 -06:00
```
2018-01-08 09:29:52 -07:00
2018-01-27 11:52:41 -07:00
Make sure to perform a clean build before running tests:
2018-10-14 22:13:21 -06:00
```
make clean build
```
2018-01-27 11:52:41 -07:00
2023-05-18 13:48:47 -06:00
## Run tests via local act_runner
### Run all jobs
```
act_runner exec -W ./.github/workflows/pull-db-tests.yml --event=pull_request --default-actions-url="https://github.com" -i catthehacker/ubuntu:runner-latest
2018-01-27 11:52:41 -07:00
```
2023-05-18 13:48:47 -06:00
Warning: This file defines many jobs, so it will be resource-intensive and therefor not recommended.
### Run single job
```SHELL
act_runner exec -W ./.github/workflows/pull-db-tests.yml --event=pull_request --default-actions-url="https://github.com" -i catthehacker/ubuntu:runner-latest -j < job_name >
```
You can list all job names via:
```SHELL
act_runner exec -W ./.github/workflows/pull-db-tests.yml --event=pull_request --default-actions-url="https://github.com" -i catthehacker/ubuntu:runner-latest -l
2018-01-27 11:52:41 -07:00
```
2022-09-02 13:18:23 -06:00
## Run sqlite integration tests
2020-02-22 15:45:20 -07:00
Start tests
2018-01-27 11:52:41 -07:00
```
make test-sqlite
```
2022-09-02 13:18:23 -06:00
## Run MySQL integration tests
2021-12-23 20:56:57 -07:00
Setup a MySQL database inside docker
2018-01-27 11:52:41 -07:00
```
2020-02-22 15:45:20 -07:00
docker run -e "MYSQL_DATABASE=test" -e "MYSQL_ALLOW_EMPTY_PASSWORD=yes" -p 3306:3306 --rm --name mysql mysql:latest #(just ctrl-c to stop db and clean the container)
2021-07-08 05:38:13 -06:00
docker run -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" --rm --name elasticsearch elasticsearch:7.6.0 #(in a second terminal, just ctrl-c to stop db and clean the container)
2018-01-27 11:52:41 -07:00
```
Start tests based on the database container
```
2019-09-25 06:13:18 -06:00
TEST_MYSQL_HOST=localhost:3306 TEST_MYSQL_DBNAME=test TEST_MYSQL_USERNAME=root TEST_MYSQL_PASSWORD='' make test-mysql
2018-01-27 11:52:41 -07:00
```
2022-09-02 13:18:23 -06:00
## Run pgsql integration tests
2018-01-27 11:52:41 -07:00
Setup a pgsql database inside docker
```
2020-02-22 15:45:20 -07:00
docker run -e "POSTGRES_DB=test" -p 5432:5432 --rm --name pgsql postgres:latest #(just ctrl-c to stop db and clean the container)
2018-01-27 11:52:41 -07:00
```
Start tests based on the database container
```
2019-09-25 06:13:18 -06:00
TEST_PGSQL_HOST=localhost:5432 TEST_PGSQL_DBNAME=test TEST_PGSQL_USERNAME=postgres TEST_PGSQL_PASSWORD=postgres make test-pgsql
```
2022-09-02 13:18:23 -06:00
## Run mssql integration tests
2019-09-25 06:13:18 -06:00
Setup a mssql database inside docker
```
2020-02-22 15:45:20 -07:00
docker run -e "ACCEPT_EULA=Y" -e "MSSQL_PID=Standard" -e "SA_PASSWORD=MwantsaSecurePassword1" -p 1433:1433 --rm --name mssql microsoft/mssql-server-linux:latest #(just ctrl-c to stop db and clean the container)
2019-09-25 06:13:18 -06:00
```
Start tests based on the database container
```
TEST_MSSQL_HOST=localhost:1433 TEST_MSSQL_DBNAME=gitea_test TEST_MSSQL_USERNAME=sa TEST_MSSQL_PASSWORD=MwantsaSecurePassword1 make test-mssql
2018-01-27 11:52:41 -07:00
```
## Running individual tests
2018-01-08 09:29:52 -07:00
2019-09-25 06:13:18 -06:00
Example command to run GPG test:
2021-12-23 20:56:57 -07:00
For SQLite:
2019-09-25 06:13:18 -06:00
2018-01-08 09:29:52 -07:00
```
2019-09-25 06:13:18 -06:00
make test-sqlite#GPG
2018-01-08 09:29:52 -07:00
```
2023-10-03 11:27:57 -06:00
For other databases(replace `mssql` to `mysql` , or `pgsql` ):
2019-09-25 06:13:18 -06:00
```
TEST_MSSQL_HOST=localhost:1433 TEST_MSSQL_DBNAME=test TEST_MSSQL_USERNAME=sa TEST_MSSQL_PASSWORD=MwantsaSecurePassword1 make test-mssql#GPG
2020-02-22 15:45:20 -07:00
```
2020-06-01 19:39:44 -06:00
## Setting timeouts for declaring long-tests and long-flushes
We appreciate that some testing machines may not be very powerful and
the default timeouts for declaring a slow test or a slow clean-up flush
may not be appropriate.
You can either:
* Within the test ini file set the following section:
```ini
[integration-tests]
SLOW_TEST = 10s ; 10s is the default value
SLOW_FLUSH = 5S ; 5s is the default value
```
* Set the following environment variables:
```bash
GITEA_SLOW_TEST_TIME="10s" GITEA_SLOW_FLUSH_TIME="5s" make test-sqlite
```
2024-02-22 17:08:17 -07:00
## Running SimpleSAML for testing SAML locally
```shell
docker run \
-p 8080:8080 \
-p 8443:8443 \
-e SIMPLESAMLPHP_SP_ENTITY_ID=http://localhost:3003/user/saml/test-sp/metadata \
-e SIMPLESAMLPHP_SP_ASSERTION_CONSUMER_SERVICE=http://localhost:3003/user/saml/test-sp/acs \
-e SIMPLESAMLPHP_SP_SINGLE_LOGOUT_SERVICE=http://localhost:3003/user/saml/test-sp/acs \
--add-host=localhost:192.168.65.2 \
-d allspice/simple-saml
```
```shell
TEST_SIMPLESAML_URL=localhost:8080 make test-sqlite#TestSAMLRegistration
```