nm17/end-to-end
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: managing legacy tests and cutting branches

Browse source
This commit is contained in:
Earl Warren 2024-04-25 12:38:58 +02:00
parent 449890d712
commit 456dab5002
No known key found for this signature in database
GPG key ID: 0579CB2928A78A00
1 changed files with 12 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

14
README.md
View file

@ -3,13 +3,23 @@
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
on [Forgejo actions](https://code.forgejo.org/actions) developed
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.
# Removing legacy tests
End to end tests cover the supported range of releases and when one of
them is EOL, it must be removed as well as the tests that target it
specifically. Otherwise the test suite would grow indefinitely.
When a release is EOL, a branch is cut with a name following the
pattern `legacy/vX.Y-vA.B`. For instance when `v8.0` is published and
`v1.21` is EOL, the branch `legacy/v8.0-v1.21` is cut.
# Hacking
docker and sudo must be installed with insecure registries allowed in
@ -46,7 +56,7 @@ 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.
It will be used whenever the version `7.0-dev` is specified in a test.
## Running actions locally