mirror of
https://github.com/element-hq/element-web.git
synced 2024-11-30 23:31:28 +03:00
1fda735222
This replaces Riot with Element in various CI scripts, modules, parameters, etc. This _should_ be the last major rebranding pass (hopefully). Fixes https://github.com/vector-im/element-web/issues/14894
1.8 KiB
1.8 KiB
Running the end-to-end tests on Windows
Windows is not the best platform to run the tests on, but if you have to, enable Windows Subsystem for Linux (WSL) and start following these steps to get going:
- Navigate to your working directory (
cd /mnt/c/users/travisr/whatever/matrix-react-sdk
for example). - Run
sudo apt-get install unzip python3 virtualenv dos2unix
- Run
dos2unix ./test/end-to-end-tests/*.sh ./test/end-to-end-tests/synapse/*.sh ./test/end-to-end-tests/element/*.sh
- Install NodeJS for ubuntu:
curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash - sudo apt-get update sudo apt-get install nodejs
- Start Element on Windows through
yarn start
- While that builds... Run:
sudo apt-get install x11-apps wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb sudo dpkg -i google-chrome-stable_current_amd64.deb sudo apt -f install
- Run:
cd ./test/end-to-end-tests ./synapse/install.sh ./install.sh ./run.sh --app-url http://localhost:8080 --no-sandbox
Note that using yarn test:e2e
probably won't work for you. You might also have to use the config.json from the
element/config-template
directory in order to actually succeed at the tests.
Also note that you'll have to use --no-sandbox
otherwise Chrome will complain that there's no sandbox available. You
could probably fix this with enough effort, or you could run a headless Chrome in the WSL container without a sandbox.
Reference material that isn't fully represented in the steps above (but snippets have been borrowed):