summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJacob Walls <jacobtylerwalls@gmail.com>2026-05-06 14:03:45 -0400
committerJacob Walls <jacobtylerwalls@gmail.com>2026-05-06 15:15:15 -0400
commit21de00b097187d1e4e479ea877df64bee22b60c9 (patch)
treedc8bca9e52c670ba28f116d517aeb3231d29c72c
parent7f66c3b41f0fb0fb938d7b96e20a28dccdaa2ecd (diff)
Refs #36620 -- Mentioned coverage workflow uses PostgreSQL.
Before c507aaf9abeff4b93b7f9bdbc55801f2ccfc2d01, this workflow used to run on SQLite.
-rw-r--r--docs/internals/contributing/writing-code/unit-tests.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/internals/contributing/writing-code/unit-tests.txt b/docs/internals/contributing/writing-code/unit-tests.txt
index 657027a033..d19616e323 100644
--- a/docs/internals/contributing/writing-code/unit-tests.txt
+++ b/docs/internals/contributing/writing-code/unit-tests.txt
@@ -419,14 +419,14 @@ the lines that were changed or added in the PR. It shows:
When reviewing coverage reports on pull requests, keep these limitations in
mind:
-* **Database-specific code:** The CI coverage job runs tests using SQLite on
- Windows. Code paths specific to other databases (PostgreSQL, MySQL, Oracle)
+* **Database-specific code:** The CI coverage job runs tests using PostgreSQL
+ on Ubuntu. Code paths specific to other databases (SQLite, MySQL, Oracle)
will appear as "not covered" even if database-specific tests exist. This is
expected and acceptable.
* **Platform-specific code:** Similarly, code that only runs on certain
- operating systems (Linux, macOS) will appear as not covered when run on
- Windows.
+ operating systems (Windows, macOS) will appear as not covered when run on
+ Ubuntu.
* **Coverage doesn't equal quality:** A line being "covered" only means it was
executed during tests. It doesn't guarantee the line is well-tested or that