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
Copy file name to clipboardExpand all lines: docs/content/doc/developers/guidelines-backend.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,8 +33,9 @@ To maintain understandable code and avoid circular dependencies it is important
33
33
34
34
-`build`: Scripts to help build Gitea.
35
35
-`cmd`: All Gitea actual sub commands includes web, doctor, serv, hooks, admin and etc. `web` will start the web service. `serv` and `hooks` will be invoked by Git or OpenSSH. Other sub commands could help to maintain Gitea.
36
-
-`tests`: Tests
37
-
-`tests/integration`: Integration tests
36
+
-`tests`: Common test utility functions
37
+
-`tests/integration`: Integration tests, to test back-end regressions
38
+
-`tests/e2e`: E2e tests, to test test front-end <> back-end compatibility and visual regressions.
38
39
-`models`: Contains the data structures used by xorm to construct database tables. It also contains functions to query and update the database. Dependencies to other Gitea code should be avoided. You can make exceptions in cases such as logging.
39
40
-`models/db`: Basic database operations. All other `models/xxx` packages should depend on this package. The `GetEngine` function should only be invoked from `models/`.
40
41
-`models/fixtures`: Sample data used in unit tests and integration tests. One `yml` file means one table which will be loaded into database when beginning the tests.
0 commit comments