forgejo/tests
Earl Warren b69e4d3058
[TESTS] increase test-sqlite log level to Trace
It does not pollute the output because they go to sqlite-log/gitea.log
and it may provide clues for debugging. When trying to figure out a
problem in production, Debug is likely to be used but in a development
environment a very fine grain log is the most useful. If that's really
too much noise, the lines can be trimmed by removing all those with [T].

(cherry picked from commit 666b02eb9d)
2023-07-26 14:40:02 +02:00
..
e2e Refactor web package and context package (#25298) 2023-06-18 09:59:09 +02:00
fuzz Move fuzz tests into tests/fuzz (#22376) 2023-01-09 15:30:14 +08:00
gitea-lfs-meta Test views of LFS files (#22196) 2022-12-23 07:41:56 +08:00
gitea-repositories-meta Fix bug of branches API with tests (#25578) 2023-07-01 10:52:52 +08:00
integration [TESTS] coverage for SignInOAuthCallback 2023-07-26 14:40:02 +02:00
mssql.ini.tmpl [CI] set PASSWORD_HASH_ALGO = argon2 for integration tests 2023-07-26 14:16:04 +02:00
mysql.ini.tmpl [CI] set PASSWORD_HASH_ALGO = argon2 for integration tests 2023-07-26 14:16:04 +02:00
mysql8.ini.tmpl [CI] set PASSWORD_HASH_ALGO = argon2 for integration tests 2023-07-26 14:16:04 +02:00
pgsql.ini.tmpl [CI] tests/pgsql.ini.tmpl: do not use minio 2023-07-26 14:16:04 +02:00
sqlite.ini.tmpl [TESTS] increase test-sqlite log level to Trace 2023-07-26 14:40:02 +02:00
test_utils.go Replace interface{} with any (#25686) 2023-07-04 18:36:08 +00:00