From 976c247f145a706f3542c38ebfa370cbeec4559a Mon Sep 17 00:00:00 2001 From: Earl Warren Date: Tue, 16 Jul 2024 17:27:22 +0200 Subject: [PATCH] developer: testing: move e2e to the README of the repository --- docs/developer/testing.md | 40 +-------------------------------------- 1 file changed, 1 insertion(+), 39 deletions(-) diff --git a/docs/developer/testing.md b/docs/developer/testing.md index 9a76cdf1..61d637d4 100644 --- a/docs/developer/testing.md +++ b/docs/developer/testing.md @@ -16,45 +16,7 @@ make test ## Frontend tests -The [e2e](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md) frontend tests are run with: - -```sh -make 'test-e2e-sqlite' -# or, for individual tests -make 'test-e2e-sqlite#example.test' -``` - -They are based on [playwright](https://playwright.dev/) and will: - -- Launch a Forgejo instance -- Populate it with data found in the `models/fixtures` directory -- Launch a browser (e.g. Firefox) -- Run JavaScript tests (e.g. tests/e2e/example.test.e2e.js) - -> **NOTE:** make sure to [use a version of Node >= 20.11.1](https://github.com/microsoft/playwright/issues/29253) - -### With VSCodium or VSCode - -To debug a test, you can use "Playwright Test" for -[VScodium](https://open-vsx.org/extension/ms-playwright/playwright) -or [VSCode](https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright). -Before doing that you will need to manually start a Forgejo instance and populate it -with data from `models/fixtures` by running: - -```sh -make TAGS='sqlite sqlite_unlock_notify' 'test-e2e-debugserver' -``` - -### CLI - -Tests can also be individually run on an existing server as follows: - -```sh -GITEA_URL=http://0.0.0.0:3000 npx playwright test tests/e2e/release.test.e2e.js -``` - -In this case the Forgejo instance must be manually prepared with a minimal -subset of the data found in the `models/fixtures` directory. +See [the e2e README](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md). ## Interactive testing