e98346e7cd
Rename login directory to auth
2019-01-21 17:46:03 -06:00
0e580635eb
Update tests for new platform layout
2018-12-18 18:13:51 +00:00
6ca0b3ad03
Update the tests to match https://github.com/matrix-org/matrix-react-sdk/pull/2340
...
See the react-sdk PR for some context.
2018-12-11 16:14:17 +00:00
1dfaf70562
Revert "Revert "Run lint on travis builds and use modern node versions""
2018-11-22 18:25:55 +00:00
f701e2601a
Revert "Run lint on travis builds and use modern node versions"
2018-11-22 18:17:09 +00:00
70fe4f67ee
eslint --fix on test/
2018-10-19 20:59:07 -05:00
c8b26a1002
fix tests
2018-04-16 00:23:34 +01:00
8757c8cae0
move notif UTs to sdk
2018-04-12 20:24:44 +01:00
f7a26ddb91
fix (race?) broken tests
...
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-11-19 20:46:40 +00:00
b9cf2c6b6c
remove 'return to app' test
2017-10-26 18:08:42 +01:00
c32e736754
Comment why we don't expect joining flag to reset
2017-09-19 10:23:12 +01:00
30efd02d22
Fix test for new behaviour of 'joining' flag
...
It's no longer reset when the join request completes, so don't
assert it. (The important test is later, asserting that the room
object is non-null).
2017-09-15 15:57:37 +01:00
238afde00a
Increase the timeout for clearing indexeddbs
...
Chrome seems to take ages (like, 1500ms regularly) to clear out the indexeddbs,
and that's causing test timeouts. Bump the timeout to hack around it.
Also: clear both dbs in parallel (can't hurt, right?) and improve diagnostics
on the process.
2017-07-20 11:01:27 +01:00
66ddf25977
Deflake the joining test
...
Just give the client longer to get started (it seems to be taking a long time
to get started talking to indexeddb)
2017-07-14 16:14:42 +01:00
32ef273f9d
use flushAllExpected in joining test
...
It won't do much to help with the vm stopping for 300ms, but it should make the
code and logs clearer.
2017-07-13 13:23:10 +01:00
76181f4771
Merge remote-tracking branch 'origin/develop' into rav/bluebird
2017-07-13 12:04:54 +01:00
69eb1a49d4
Fix a broken test
...
turns out that you could call defer.resolve on q defers as an unbound function,
whereas that doesn't work with bluebird promises.
2017-07-13 00:56:13 +01:00
4c5b5ca0ba
replace `q.Promise` with `new Promise`
2017-07-13 00:50:01 +01:00
d5b550f89a
replace q method calls with bluebird ones
...
```
find src test -name '*.js' |
xargs perl -i -pe 's/q\.(all|defer|reject|delay|try|isFulfilled)\(/Promise.$1(/'
```
2017-07-13 00:50:01 +01:00
b29b4a959b
q(...) -> Promise.resolve
...
```
find src test -name '*.js' | xargs perl -i -pe 's/\b[qQ]\(/Promise.resolve(/'
```
2017-07-13 00:50:01 +01:00
10decf95f6
replace imports of `q` with bluebird
...
update `package.json`
```
find src test -name '*.js' |
xargs perl -i -pe 'if (/require\(.[qQ].\)/) { $_ = "import Promise from '\''bluebird'\'';\n"; }'
find src test -name '*.js' |
xargs perl -i -pe 'if (/import [qQ] /) { $_ = "import Promise from '\''bluebird'\'';\n"; }'
```
2017-07-13 00:48:31 +01:00
b2403d59b7
loading tests: wait for login component
...
Rather than a fixed delay, use matrix-react-test-utils to wait for the login
component to appear. Hopefully this will deflakify some tests.
2017-07-13 00:18:49 +01:00
bd1196716a
Use external mock-request
...
mock-request is now factored out to matrix-mock-request; use it
2017-07-04 15:59:21 +01:00
ca3399df77
Clean up some log outputs from the integ tests
2017-06-20 17:41:21 +01:00
abf21675d5
Add some more logging to the tests
...
... to help diagnose when they fail
2017-06-20 16:24:04 +01:00
557d4ae4c1
Test 'return-to-app' functionality
...
Add a test for the 'log in as user' functionality, as well as the 'return to
app' functionality.
2017-06-19 10:47:36 +01:00
5a8a41ad50
Merge branch 'develop' into rav/fix_token_redirect
2017-06-19 09:05:19 +01:00
60be24c665
Rename promise
2017-06-19 09:04:24 +01:00
6df1574b8b
onLoadCompleted is now onTokenLoginCompleted
2017-06-16 15:05:14 +01:00
f5b2a92e84
Give the login panel a bit longer to appear
2017-06-15 18:17:00 +01:00
1fcd462660
Tweak tests to match updates to matrixchat
...
Mostly this is just making it look at the `view` state rather than the
individual boolean flags.
One other tweak merits explanation: we now implement the initial
couldn't-register-as-guest login with an explicit switch to the LOGIN view,
which means that the URL gets updated to #/login.
2017-06-15 17:52:18 +01:00
584e4c04da
Merge pull request #4313 from vector-im/rav/deflakify_joining_test
...
Attempts to deflakify the joining test
2017-06-15 16:29:37 +01:00
a7a7ffd84b
Merge pull request #4315 from vector-im/rav/test_rts_login
...
Add a test for the login flow when there is a teamserver
2017-06-15 16:13:05 +01:00
a28af8bcc6
Extend timeouts in joining tests again
...
this seems to work? maybe?
2017-06-15 16:01:26 +01:00
43f56483aa
Merge branch 'develop' into rav/deflakify_joining_test
2017-06-15 15:48:13 +01:00
ca736cfce8
fix test description
...
logs in, not registers
2017-06-15 14:54:32 +01:00
98e694646c
Add a test for the login flow when there is a teamserver
...
- just to check it keeps working.
2017-06-15 02:17:24 +01:00
6f2eee1f03
Attempts to deflakify the joining test
...
Treat the waitTime passed into `flush` as a timeout rather than a
time-between-loops, so that we can pass in bigger times and not slow the tests
down too much.
Bump the timeout when waiting for /publicRooms and /initialSync in the joining
test.
2017-06-14 22:58:12 +01:00
4ca009b9f7
Remove onload simulator from loading test
...
This used to exist to reproduce the functionality in the window.onload handler
in vector/index.js -- which got removed in 31915db
2017-06-14 18:01:44 +01:00
5ff59b0c23
Tests: delete indexeddbs after running
2017-06-14 17:08:49 +01:00
27d5704978
Improve logging in mock-request
...
Try to make it a bit more obvious what's been going on in mock-request: add
timestamps to lines, and an identifier so that where we have two flushes in
parallel, we can see what's what.
2017-06-14 16:59:46 +01:00
59da904353
Check that we don't register a guest account on /#/login ( #4306 )
...
If you go straight to a /#/login link, we shoudn't go registering guest
accounts or reanimating the saved creds.
2017-06-14 16:59:00 +01:00
aa07266f12
Test that we handle stored mx_last_room_id correctly
...
* Do we show the last room correctly on resume?
* Do we show the home page if we have no last room?
* If we follow a login link, and re-log-in, do we correctly vape the
mx_last_room_id (#4283 )
2017-06-13 12:52:35 +01:00
de334cccfd
Expect to see HTTP /join/#some:alias when we the view knows it
2017-06-08 18:01:55 +01:00
8e288e14bf
Add more hacky q.delays
...
To work around the fact that we now do more trips around the
event loop to update view state (because of going vis the store).
Also add comment saying how horrible this is.
2017-06-06 15:59:24 +01:00
15d0bd9271
Partially revert https://github.com/vector-im/riot-web/pull/4201
...
The q.delay is needed to make sure (or at least reasonably
sure...) that the login component has appeared by that point. The
done handler needs to be the error callback too otherwise failures
result in timeouts rather than the actual failure.
2017-06-06 15:54:45 +01:00
feaff9d99d
Fix tests for new-guest-access
...
This time the test wasn't being flaky, but it does inspect a lot of the internal of RoomView, which has had some modifications recently. I've updated the test to reflect this and it passes locally.
Also, fix a bug in HomePage with an undeclared "error" which should be "err".
Let's see what Travis thinks of this!
2017-06-05 20:16:44 +01:00
6cc7fa3a36
Expect a HomePage now instead of a directory, because one is now shown by default
2017-05-30 12:55:50 +01:00
e07f9a8bc9
Pass through i18n keys in karma tests
2017-05-26 15:29:58 +01:00
9c7731e141
Don't include src in the test resolve root
...
As https://github.com/matrix-org/matrix-react-sdk/pull/931
2017-05-26 14:02:03 +01:00
J. Ryan Stinnett