You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|``make test[\#TestSpecificName]``| run unit test |
89
-
|``make test-sqlite[\#TestSpecificName]``| run [integration](integrations) test for SQLite |
90
-
|[More details about integrations](integrations/README.md)|
89
+
|``make test-sqlite[\#TestSpecificName]``| run [integration](tests/integration) test for SQLite |
90
+
|[More details about integration tests](tests/integration/README.md)|
91
+
|``make test-e2e-sqlite[\#TestSpecificFileName]``| run [end-to-end](tests/e2e) test for SQLite |
92
+
|[More details about e2e tests](tests/e2e/README.md)|
91
93
92
94
## Vendoring
93
95
@@ -168,7 +170,7 @@ import (
168
170
169
171
To maintain understandable code and avoid circular dependencies it is important to have a good structure of the code. The Gitea code is divided into the following parts:
170
172
171
-
-**integration:**Integrations tests
173
+
-**integration:**Integration tests
172
174
-**models:** Contains the data structures used by xorm to construct database tables. It also contains supporting functions to query and update the database. Dependencies to other code in Gitea should be avoided although some modules might be needed (for example for logging).
173
175
-**models/fixtures:** Sample model data used in integration tests.
174
176
-**models/migrations:** Handling of database migrations between versions. PRs that changes a database structure shall also have a migration step.
0 commit comments