1a1f2254e5
Remove karma junit output
...
See https://github.com/matrix-org/matrix-react-sdk/pull/2944
2019-05-03 11:40:53 +01:00
1fb8b23d4c
Set up BuildKite for Chrome
2019-03-13 22:03:37 -06:00
1312ba537a
Update scripts and docs to use `yarn` where appropriate
...
Most `npm` operations are replaced with `yarn`, which generally has better
behavior. However, steps like publish that write to the NPM registry are left to
`npm`, which currently handles these tasks best.
2019-03-12 11:06:57 +00:00
6aff7460fe
Map welcome page in Karma for less 404s
2019-02-11 11:17:40 +00:00
9e916cdd5c
make sure karma runs tests in dev mode to speed up build
2018-09-26 01:39:05 +01:00
02a185f2fe
Update Webpack to version 4
2018-04-27 11:32:59 +02:00
5c341154b7
fix theming during tests correctly
2018-04-16 00:19:08 +01:00
8684fae473
kill theming 404s when UTing
2018-04-16 00:14:09 +01:00
0243ec0096
switch karma image loc
2018-04-15 23:52:52 +01:00
06ef674597
Enable fancy karma reporters
...
cargo-cult luke's stuff from react-sdk
2017-08-08 19:05:58 +01:00
df33d40285
Enable karma-sourcemap-loader
...
This turns (some) stacktraces back into something useful, so that unpicking
test failures is vaguely tractable
2017-08-08 19:05:49 +01:00
38b1ca9b90
Use headless chrome instead of phantomjs for tests
2017-07-05 09:35:51 +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
1c2de1e483
Refactor karma config
...
- rename test:multi npm target to test-multi, for consistency with react-sdk
- base karma webpack config on the distribution one
- include Olm if we have it
- don't use the karma source loader - it's pointless given we webpack
everything.
- turn off module listing in the webpack stats to shorten the console output
2017-02-02 23:33:12 +00:00
237f4df08e
A couple of tweaks to the karma config
...
* allow the imgs to be served from the karma server to avoid 404s
* Use the source-map-loader for js
2017-01-18 21:42:14 +00:00
18450058d7
Remove presets from karma.conf
...
seemt o be picked up from .babelrc
2016-10-17 16:28:14 +01:00
ea09a25563
Revert "Switch to babel 6"
2016-10-14 18:50:22 +01:00
0c3537ac1a
Remove presets from karma.conf
...
seemt o be picked up from .babelrc
2016-10-13 09:51:10 +01:00
795986f146
Karma: fix warning by ignoring olm
...
If olm is not installed, the webpack build for the karma tests gives an ugly
error. None of the tests currently care if olm is installed or not, so fix this
for now by just ignoring the olm module.
2016-06-16 07:41:34 +01:00
0635a6f562
Fix karma tests
...
As we now use draft-js: https://github.com/facebook/fbjs/issues/133#event-617440260
2016-06-14 16:32:07 +01:00
29ff9c11a8
Final karma tweaks
...
* fix a comment
* drop redundant import
2016-04-13 18:22:05 +01:00
bf31d6d5fa
Karma test tweaks
...
* Make sure we only get one js-sdk (and update runtime config to match)
* Don't verifyNoOutstandingRequests (since it is hard to be certain which we
will get, and makes the tests too dependent on implementation-specifics).
* Disable color for npm test, to avoid confusing Jenkins
2016-04-13 17:41:23 +01:00
322af6513d
Run some tests under karma
...
Including a regression test for
https://github.com/vector-im/vector-web/issues/1314
2016-04-13 17:20:06 +01:00
69ce3c43cf
Revert "Merge branch 'develop' into rav/karma"
...
The karma tests don't pass yet, and aren't ready to land on develop.
This reverts commit 438453e61a50f94eb040
2016-04-13 17:17:45 +01:00
429d110212
Run some tests under karma
...
Including a regression test for
https://github.com/vector-im/vector-web/issues/1314
2016-04-13 10:15:04 +01:00
David Baker