Matrix/element-web-Github
1
0
Fork 0
mirror of https://github.com/vector-im/element-web.git synced 2024-11-29 14:00:48 +08:00
Code Issues Packages Projects Releases Wiki Activity
94 Commits 216 Branches 561 Tags 454 MiB
TypeScript 91.2%
CSS 6.2%
HTML 1.3%
JavaScript 1%
f49b85897d
Go to file
Bruno Windels f49b85897d remove specific timeout for selectors 
as these are not hard sleeps, but timeouts, its better to put them
a bit larger, as in the best case they'll return quickly anyway
and in the worst case where they need a lot of time it's still better
if the tests don't fail
2018-08-23 00:29:24 +02:00
riot bring indentation in line with other front-end projects 2018-08-14 12:53:16 +02:00
src remove specific timeout for selectors 2018-08-23 00:29:24 +02:00
synapse bring indentation in line with other front-end projects 2018-08-14 12:53:16 +02:00
.editorconfig bring indentation in line with other front-end projects 2018-08-14 12:53:16 +02:00
.gitignore add ignore file 2018-07-09 17:08:16 +02:00
install.sh exit on error 2018-07-31 10:35:21 +02:00
package.json add argument for passing riot server, makes local testing easier 2018-08-15 11:26:46 +02:00
README.md make scripts executable, running them with sh does something weird on travis 2018-07-31 10:35:21 +02:00
run.sh stop servers on error in run script 2018-07-31 10:35:21 +02:00
start.js didnt mean to commit this 2018-08-15 12:21:08 +02:00

README.md

Matrix React Web App End-to-End tests

This repository contains tests for the matrix-react-sdk web app. The tests fire up a headless chrome and simulate user interaction (end-to-end). Note that end-to-end has little to do with the end-to-end encryption matrix supports, just that we test the full stack, going from user interaction to expected DOM in the browser.

Current tests

  • test riot loads (check title)
  • signup with custom homeserver
  • join preexisting room

Roadmap

  • get rid of jest, as a test framework won't be helpful to have a continuous flow going from one use case to another (think: do login, create a room, invite a user, ...). a test framework usually assumes the tests are semi-indepedent.
  • better error reporting (show console.log, XHR requests, partial DOM, screenshot) on error
  • cleanup helper methods
  • add more css id's/classes to riot web to make css selectors in test less brittle.
  • avoid delay when waiting for location.hash to change
  • more tests!
  • setup installing & running riot and synapse as part of the tests.
    • Run 2 synapse instances to test federation use cases.
    • start synapse with clean config/database on every test run
  • look into CI(Travis) integration
  • create interactive mode, where window is opened, and browser is kept open until Ctrl^C, for easy test debugging.

It's broken! How do I see what's happening in the browser?

Look for this line:

puppeteer.launch();

Now change it to:

puppeteer.launch({headless: false});

How to run

Setup

Run ./install.sh. This will:

  • 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.
  • install riot, this fetches the master branch at the moment.
  • install dependencies (will download copy of chrome)

Run tests

Run tests with ./run.sh.

Developer Guide

Please follow the standard Matrix contributor's guide: https://github.com/matrix-org/synapse/tree/master/CONTRIBUTING.rst

Please follow the Matrix JS/React code style as per: https://github.com/matrix-org/matrix-react-sdk/blob/master/code_style.md