A web client for Matrix used to replace WhatsApp https://riot.opencloud.lu/
 
 
 
 
Go to file
Bruno Windels b42a0411f3 add IDEA for better debugging to readme (unrelated to PR really) 2018-07-23 10:10:36 +02:00
riot disable welcomeUserId for now in riot config, flow seems broken 2018-07-23 10:09:30 +02:00
synapse prevent stop scripts from polluting output 2018-07-23 09:41:25 +02:00
tests remove obsolete code 2018-07-23 10:09:52 +02:00
.gitignore add ignore file 2018-07-09 17:08:16 +02:00
README.md add IDEA for better debugging to readme (unrelated to PR really) 2018-07-23 10:10:36 +02:00
code_style.md add code style 2018-07-09 17:08:16 +02:00
helpers.js working consent test by accepting server notices invite and clicking on link, also create room 2018-07-20 18:51:25 +02:00
package.json don't use jest and just run test code sequentially 2018-07-09 17:43:21 +02:00
run.sh make script runnable in one terminal, without server output garbling up test results. This won't work well on CI server but makes it clear to run locally 2018-07-20 19:00:27 +02:00
start.js turn headless back on 2018-07-20 18:59:45 +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

  • install synapse with sh synapse/install.sh, this 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 with sh riot/install.sh, this fetches the master branch at the moment.
  • install dependencies with npm install (will download copy of chrome)
  • have riot-web running on localhost:8080
  • have a local synapse running at localhost:8008

Run tests

Run tests with sh run.sh.

You should see the terminal split with on top the server output (both riot static server, and synapse), and on the bottom the tests running.