Forgejo end-to-end tests
Go to file
2024-04-06 09:58:04 +00:00
.forgejo tests: the development branch requires go 1.22 to build 2024-03-25 18:26:07 +01:00
actions Revert "actions: workaround for possible 404 transient bug on artifacts" 2024-04-05 05:24:04 +02:00
forgejo the forgejo development branch is now 8.0 2024-03-30 14:44:43 +01:00
lib logs: show logs, not just the .out files 2024-04-06 11:08:05 +02:00
packages Merge pull request 'merge actions test into' (#112) from twenty-panda/end-to-end:wip-actions into main 2024-03-20 13:18:28 +00:00
storage merge actions test into 2024-03-20 13:42:44 +01:00
upgrade run pprof test on test build 2024-04-02 20:15:57 +02:00
.editorconfig add editorconfig to help with Forgejo space display 2024-02-28 18:49:46 +01:00
.gitignore upgrades: remove ad-hoc code and use instead 2024-03-15 10:21:58 +07:00 merge actions test into 2024-03-20 13:42:44 +01:00
LICENSE import from forgejo 2023-10-26 21:21:20 +02:00 merge actions test into 2024-03-20 13:42:44 +01:00

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.


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": [ "" ]

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 script.

git clone
export PATH=$(pwd)/setup-forgejo:$PATH
git clone
cd end-to-end

Running from locally built binary

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 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.

./ actions_setup 1.21
firefox # user root / admin1234
./ actions_verify_example artifacts
./ 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

./ test_packages_alpine
./ test_storage_stable_s3 minio

Cleanup. It will teardown the Forgejo instance.

./ stop