Forgejo end-to-end tests

Find a file

Twenty Panda bf689a2478 refactor end-to-end.yml workflow to use a top-level end-to-end.sh		2024-03-17 16:27:35 +01:00
.forgejo	refactor end-to-end.yml workflow to use a top-level end-to-end.sh	2024-03-17 16:27:35 +01:00
actions	Forgejo v1.22 will actually be Forgejo v7.0	2024-02-28 17:38:31 +01:00
forgejo	refactor end-to-end.yml workflow to use a top-level end-to-end.sh	2024-03-17 16:27:35 +01:00
lib	refactor end-to-end.yml workflow to use a top-level end-to-end.sh	2024-03-17 16:27:35 +01:00
packages	packages: simplify the setup to use the same as upgrades	2024-03-15 19:54:34 +07:00
.gitignore	upgrades: remove ad-hoc code and use forgejo-curl.sh instead	2024-03-15 10:21:58 +07:00
end-to-end.sh	refactor end-to-end.yml workflow to use a top-level end-to-end.sh	2024-03-17 16:27:35 +01:00
LICENSE	import from forgejo	2023-10-26 21:21:20 +02:00
README.md	refactor end-to-end.yml workflow to use a top-level end-to-end.sh	2024-03-17 16:27:35 +01:00

README.md

Forgejo end-to-end tests

A series of tests scenarios and assertions covering Forgejo and the Forgejo runner. They partially rely on Forgejo actions developped specifically for testing such as 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:

{
  "insecure-registries": [ "10.0.0.0/8" ]
}

Use setup-forgejo from source.

The setup-forgejo repository is a Forgejo Action 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 actions/run.sh script.

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
export DIR=/tmp/forgejo-end-to-end
rm -fr /tmp/forgejo-end-to-end ; sudo rm -fr /srv/example ; sudo mkdir /srv/example ; sudo chown -R $USER /srv/example

Run using Forgejo built from source.

make TAGS='bindata sqlite sqlite_unlock_notify' generate forgejo
cp -a forgejo $DIR/forgejo

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.

Run one example

actions/run.sh https://codeberg.org/forgejo-experimental/forgejo/releases/download/v7.0.0-test/forgejo-7.0.0-test-linux-amd64 v7.0.0-test v7_0 cron # runs actions/example-cron

Cleanup. It will teardown Forgejo & the runner and not run them because there is nothing to test.

actions/run.sh https://codeberg.org/forgejo-experimental/forgejo/releases/download/v7.0.0-test/forgejo-7.0.0-test-linux-amd64 v7.0.0-test v7_0 none

Run all examples for v7_0

actions/run.sh https://codeberg.org/forgejo-experimental/forgejo/releases/download/v7.0.0-test/forgejo-7.0.0-test-linux-amd64 v7.0.0-test v7_0

Run from sources

make TAGS='bindata sqlite sqlite_unlock_notify' generate forgejo
cp -a forgejo $DIR/forgejo

Remote testing

To reduce the runtime the following variables can be set to control the number of cases run by the actions tests. If set to none they are not run at all for that version of Forgejo. If it does not exist, all tests are run.

v7_0_TESTS
V1_21_TESTS
V1_20_TESTS

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

VERBOSE=true ./forgejo/upgrades/test-upgrade.sh test_packages_alpine
VERBOSE=true ./forgejo/upgrades/test-upgrade.sh test_storage_stable_s3 minio

Cleanup. It will teardown the Forgejo instance.

./forgejo/upgrades/test-upgrade.sh stop