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
This replaces Riot with Element in various CI scripts, modules, parameters, etc.
This _should_ be the last major rebranding pass (hopefully).
Fixeselement-hq/element-web#14894
Copy file name to clipboardExpand all lines: test/end-to-end-tests/README.md
+5-6
Original file line number
Diff line number
Diff line change
@@ -5,17 +5,17 @@ This directory contains tests for matrix-react-sdk. The tests fire up a headless
5
5
## Setup
6
6
7
7
Run `./install.sh`. This will:
8
-
- install Synapse, fetches the master branch at the moment. If anything fails here, please refer to the Synapse README to see if you're missing one of the prerequisites.
9
-
- install Riot, this fetches the master branch at the moment.
10
-
- install dependencies (will download copy of chrome)
8
+
- install Synapse, fetches the develop branch at the moment. If anything fails here, please refer to the Synapse README to see if you're missing one of the prerequisites.
9
+
- install Element Web, this fetches the develop branch at the moment.
10
+
- install dependencies (will download copy of Chrome)
11
11
12
12
## Running the tests
13
13
14
14
Run tests with `./run.sh`.
15
15
16
16
### Debug tests locally.
17
17
18
-
`./run.sh` will run the tests against the Riot copy present in `riot/riot-web` served by a static Python HTTP server. You can symlink your `riot-web` develop copy here but that doesn't work well with Webpack recompiling. You can run the test runner directly and specify parameters to get more insight into a failure or run the tests against your local Webpack server.
18
+
`./run.sh` will run the tests against the Element copy present in `element/element-web` served by a static Python HTTP server. You can symlink your `element-web` develop copy here but that doesn't work well with Webpack recompiling. You can run the test runner directly and specify parameters to get more insight into a failure or run the tests against your local Webpack server.
19
19
20
20
```
21
21
./synapse/stop.sh && \
@@ -26,8 +26,7 @@ It's important to always stop and start Synapse before each run of the tests to
26
26
27
27
start.js accepts these parameters (and more, see `node start.js --help`) that can help running the tests locally:
28
28
29
-
-`--riot-url <url>` don't use the Riot copy and static server provided by the tests, but use a running server like the Webpack watch server to run the tests against. Make sure to have the following local config:
30
-
-`welcomeUserId` disabled as the tests assume there is no riot-bot currently.
29
+
-`--app-url <url>` don't use the Element Web copy and static server provided by the tests, but use a running server like the Webpack watch server to run the tests against.
31
30
-`--slow-mo` type at a human speed, useful with `--windowed`.
32
31
-`--throttle-cpu <factor>` throttle cpu in the browser by the given factor. Useful to reproduce failures because of insufficient timeouts happening on the slower CI server.
33
32
-`--windowed` run the tests in an actual browser window Try to limit interacting with the windows while the tests are running. Hovering over the window tends to fail the tests, dragging the title bar should be fine though.
0 commit comments