clone/logseq
1
0
Fork 0
mirror of https://github.com/logseq/logseq.git synced 2026-02-01 22:47:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: remove unused e2e-test namespace

Browse Source 
workflow step and docs for tests deleted in #11903
This commit is contained in:
Gabriel Horner
2025-07-08 08:51:29 -04:00
parent 879c3ce424
commit f736895b1b
7 changed files with 4 additions and 147 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
docs/dev-practices.md
View File

@@ -139,32 +139,8 @@ We have unit, performance and end to end tests.
### End to End Tests
Even though we have a nightly release channel, it's hard for testing users (thanks to the brave users!) to notice all issues in a limited time, as Logseq is covering so many features.
The only solution is automatic end-to-end tests - adding tests for GUI software is always painful but necessary. See https://github.com/logseq/logseq/pulls?q=E2E for e2e test examples.
To run end to end tests
```sh
yarn electron-watch
# in another shell
yarn e2e-test # or npx playwright test
```
If e2e failed after first running:
- `rm -rdf ~/.logseq`
- `rm -rdf ~/.config/Logseq`
- `rm -rdf <repo dir>/tmp/`
- Windows: `rmdir /s %APPDATA%/Electron` (Reference: https://www.electronjs.org/de/docs/latest/api/app#appgetpathname)
There's a `traceAll()` helper function to enable playwright trace file dump for specific test files https://github.com/logseq/logseq/pull/8332
If e2e tests fail in the file, they can be debugged by examining a trace dump with [the
playwright trace
viewer](https://playwright.dev/docs/trace-viewer#recording-a-trace).
Locally this will get dumped into e2e-dump/.
On CI the trace file will be under Artifacts at the bottom of a run page e.g.
https://github.com/logseq/logseq/actions/runs/3574600322.
To run end to end tests, see [clj-e2e tests](/clj-e2e/README.md).
### Unit Testing