Twenty Panda
96f91063c9
* replace the high level test running actions tests with end-to-end.sh * set DOMAIN to the IP instead of 127.0.0.1 for runner <-> forgejo communications * move forgejo_cli from a function to a file so that it can be used by forgejo-runner.sh * keep the documentation updates workflows separate because they need to open one PR per version
83 lines
2.5 KiB
Markdown
83 lines
2.5 KiB
Markdown
# Forgejo end-to-end tests
|
|
|
|
A series of tests scenarios and assertions covering
|
|
[Forgejo](https://codeberg.org/forgejo/forgejo) and the [Forgejo
|
|
runner](https://code.forgejo.org/forgejo/runner). They partially rely
|
|
on [Forgejo actions](https://code.forgejo.org/actions) developped
|
|
specifically for testing such as
|
|
[setup-forgejo](https://code.forgejo.org/actions/setup-forgejo).
|
|
|
|
They are designed to run using Forgejo releases and development
|
|
versions compiled from designated repositories.
|
|
|
|
# Hacking
|
|
|
|
docker and sudo must be installed with insecure registries allowed in
|
|
/etc/docker/daemon.json for the IP that will be used for forgejo such
|
|
as:
|
|
|
|
```json
|
|
{
|
|
"insecure-registries": [ "10.0.0.0/8" ]
|
|
}
|
|
```
|
|
|
|
Use setup-forgejo from source.
|
|
|
|
The [setup-forgejo](https://code.forgejo.org/actions/setup-forgejo)
|
|
repository is a [Forgejo
|
|
Action](https://forgejo.org/docs/v1.21/user/actions/) which is meant
|
|
to be used in workflows. However, it is implemented as shell scripts that
|
|
can also be used to create Forgejo instances and runners locally. This
|
|
is convenient for testing and the reason why it needs to be added to the PATH.
|
|
For instance, it is a dependency of the `end-to-end.sh` script.
|
|
|
|
```sh
|
|
git clone https://code.forgejo.org/actions/setup-forgejo
|
|
export PATH=$(pwd)/setup-forgejo:$PATH
|
|
git clone https://code.forgejo.org/forgejo/end-to-end
|
|
cd end-to-end
|
|
```
|
|
|
|
## Running from locally built binary
|
|
|
|
```sh
|
|
make TAGS='bindata sqlite sqlite_unlock_notify' generate forgejo
|
|
cp -a forgejo /srv/forgejo-binaries/forgejo-7.0-dev
|
|
```
|
|
|
|
It will be used whenver the version `7.0-dev` is specified in a test.
|
|
|
|
## Running actions locally
|
|
|
|
To run and debug workflows from `actions/example-*`, from the root of
|
|
the source directory, with docker and forgejo-curl.sh installed, mimic
|
|
what `.forgejo/workflows/actions.yml` does. There may be some manual
|
|
tweaking (such as creating temporary directories) because the tests
|
|
run as root in the context of Forgejo Actions and assume they have
|
|
admin permissions. But they do not need to run as root and must work
|
|
fine when run as a regular user.
|
|
|
|
```sh
|
|
./end-to-end.sh actions_setup 1.21
|
|
firefox 0.0.0.0:3000 # user root / admin1234
|
|
./end-to-end.sh actions_verify_example artifacts
|
|
./end-to-end.sh actions_teardown
|
|
```
|
|
## Running other tests locally
|
|
|
|
To run and debug tests, from the root of the source directory.
|
|
|
|
Run one test. When the test fails the instance can be inspected at http://0.0.0.0:3000
|
|
|
|
```sh
|
|
./end-to-end.sh test_packages_alpine
|
|
./end-to-end.sh test_storage_stable_s3 minio
|
|
```
|
|
|
|
Cleanup. It will teardown the Forgejo instance.
|
|
|
|
```sh
|
|
./end-to-end.sh stop
|
|
```
|