watcha
/
watcha-matrix-react-sdk
mirror of https://github.com/watcha-fr/matrix-react-sdk
1
1
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
27 Commits
5 Branches
9 Tags
235 MiB
 
 
 
Tag: Branch: Tree: 5f2fcefb4e
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '5f2fcefb4e'
${ noResults }
Bruno Windels 5f2fcefb4e
update instructions 		8 years ago
riot add template config file for riot installation 8 years ago
synapse add script to clear synapse db 8 years ago
tests working consent test by accepting server notices invite and clicking on link, also create room 8 years ago
.gitignore add ignore file 8 years ago
README.md update instructions 8 years ago
code_style.md add code style 8 years ago
helpers.js working consent test by accepting server notices invite and clicking on link, also create room 8 years ago
package.json don't use jest and just run test code sequentially 8 years ago
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 8 years ago
start.js turn headless back on 8 years ago

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

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.
  • 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.