This changes the way tests wait for login to complete from a timer-based system (which can cause intermittent failures) to an action-based system. The lifecycle code dispatches the action `on_logged_in` when login completes which we can wait for in the tests as a much better indication that work is done. |
||
|---|---|---|
| .. | ||
| joining.js | ||
| loading.js | ||