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
chore: update e2e test configs to better work with CI (#1458)
* Also adds a helpful test:e2e:ci script to test playwright tests inside of a docker image with a clean build to more closely resemble running in CI
* Upgrades playwright version
Copy file name to clipboardExpand all lines: packages/app/tests/e2e/README.md
+25-4Lines changed: 25 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,8 @@
1
1
# End-to-End Testing
2
2
3
-
This directory contains Playwright-based end-to-end tests for the HyperDX application. The tests are organized into core functionality and feature-specific test suites.
3
+
This directory contains Playwright-based end-to-end tests for the HyperDX
4
+
application. The tests are organized into core functionality and
Tests tagged with `@local-mode` can run against the local development server without external dependencies. The test configuration automatically starts a local development server with `NEXT_PUBLIC_IS_LOCAL_MODE=true`.
52
+
Tests tagged with `@local-mode` can run against the local development server
53
+
without external dependencies. The test configuration automatically starts a
54
+
local development server with `NEXT_PUBLIC_IS_LOCAL_MODE=true`.
51
55
52
56
## Test Organization
53
57
@@ -87,6 +91,15 @@ Run tests in debug mode with browser developer tools:
87
91
yarn test:e2e:debug
88
92
```
89
93
94
+
### CI Mode
95
+
96
+
Run tests in ci mode, which runs it in a docker container and environment
97
+
similar to how it runs inside of Github Actions
98
+
99
+
```bash
100
+
yarn test:e2e:ci
101
+
```
102
+
90
103
### Single Test Debugging
91
104
92
105
To debug a specific test file:
@@ -114,6 +127,7 @@ yarn playwright show-report
114
127
```
115
128
116
129
The report includes:
130
+
117
131
- Test execution timeline
118
132
- Screenshots of failures
119
133
- Video recordings of failed tests
@@ -122,6 +136,7 @@ The report includes:
122
136
### Test Results
123
137
124
138
Test artifacts are stored in:
139
+
125
140
-`test-results/` - Screenshots, videos, and traces for failed tests
0 commit comments