Skip to content

Commit 1a4e2bf

Browse files
authored
tests: s/GITEA_UNIT_TESTS_VERBOSE/GITEA_UNIT_TESTS_LOG_SQL/ (#18142)
The GITEA_UNIT_TESTS_VERBOSE variable is an undocumented variable introduced in 2017 (see 1028ef2) whose sole purpose has been to log SQL statements when running unit tests. It is renamed for clarity and a warning is displayed for backward compatibility for people and scripts that know about it. The documentation is updated to reflect this change.
1 parent fb2dc95 commit 1a4e2bf

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/content/doc/developers/hacking-on-gitea.en-us.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -277,7 +277,7 @@ There are two types of test run by Gitea: Unit tests and Integration Tests.
277277
### Unit Tests
278278

279279
Unit tests are covered by `*_test.go` in `go test` system.
280-
You can set environment variable `GITEA_UNIT_TESTS_VERBOSE=1` to see detail logs during the test.
280+
You can set the environment variable `GITEA_UNIT_TESTS_LOG_SQL=1` to display all SQL statements when running the tests in verbose mode (i.e. when `GOTESTFLAGS=-v` is set).
281281

282282
```bash
283283
TAGS="bindata sqlite sqlite_unlock_notify" make test # Runs the unit tests

models/unittest/testdb.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -152,7 +152,7 @@ func CreateTestEngine(opts FixturesOptions) error {
152152
if err = db.SyncAllTables(); err != nil {
153153
return err
154154
}
155-
switch os.Getenv("GITEA_UNIT_TESTS_VERBOSE") {
155+
switch os.Getenv("GITEA_UNIT_TESTS_LOG_SQL") {
156156
case "true", "1":
157157
x.ShowSQL(true)
158158
}

0 commit comments

Comments
 (0)