forgejo/tests
Earl Warren 60463e3bab
[DB] run all Forgejo migrations in integration tests
The tests at tests/integration/migration-test/migration_test.go will
not run any Forgejo migration when using the gitea-*.sql.gz files
because they do not contain a ForgejoVersion row which is interpreted
as a new Forgejo installation for which there is no need for migration.

Create a situation by which the ForgejoVersion table exists and has a
version of 0 in tests/integration/migration-test/forgejo-v1.19.0.*.sql.gz
thus ensuring all Forgejo migrations are run.

The forgejo*.sql.gz files do not have any Gitea related records, which
will be interpreted by the Gitea migrations as a new installation that
does not need any migration. As a consequence the migration tests run
when using forgejo-v1.19.0.*.sql.gz are exclusively about Forgejo
migrations.

(cherry picked from commit ec8003859c)
(cherry picked from commit 697570ff39)
(cherry picked from commit f041aec172)
2023-08-29 08:47:10 +02:00
..
e2e Update minimum password length requirements (#25946) 2023-08-21 19:27:50 +00:00
fuzz
gitea-lfs-meta
gitea-repositories-meta Add commits dropdown in PR files view and allow commit by commit review (#25528) 2023-07-28 21:18:12 +02:00
integration [DB] run all Forgejo migrations in integration tests 2023-08-29 08:47:10 +02:00
mssql.ini.tmpl [CI] set PASSWORD_HASH_ALGO = argon2 for integration tests 2023-08-29 08:22:03 +02:00
mysql.ini.tmpl [CI] set PASSWORD_HASH_ALGO = argon2 for integration tests 2023-08-29 08:22:03 +02:00
mysql8.ini.tmpl [CI] set PASSWORD_HASH_ALGO = argon2 for integration tests 2023-08-29 08:22:03 +02:00
pgsql.ini.tmpl [CI] set PASSWORD_HASH_ALGO = argon2 for integration tests 2023-08-29 08:22:03 +02:00
sqlite.ini.tmpl [TESTS] increase test-sqlite log level to Trace 2023-08-29 08:47:10 +02:00
test_utils.go Refactor tests (#26464) 2023-08-12 16:30:16 +00:00