Commit graph

14 commits

Author SHA1 Message Date
Richard van der Hoff
66966eecf8 Make sure we only have one React in tests
Otherwise if we symlink in react-gemini-scrollbar, React gets very confused
2016-04-21 08:10:58 +01:00
Richard van der Hoff
7a821ce9d1 Make it possible to only run one test file each time 2016-04-07 17:49:39 +01:00
Richard van der Hoff
ae1220a6a4 Fix test for npm 3
npm 3 puts files in slightly saner places, so we have to look for the gemini
css in two places
2016-04-05 11:08:02 +01:00
Richard van der Hoff
51fe77122b Fix an issue where the scroll stopped working.
Under certain conditions, it was possible to get stuck in a state where any
user-initiated scroll would be met with "Working around
vector-im/vector-web#528" and overridden. Fix this by removing the duplication
between _lastSetScroll and recentEventScroll, and using _lastSetScroll which is
more reliable.
2016-04-05 10:41:32 +01:00
Richard van der Hoff
73f7528d0f Use babel 5 for karma tests 2016-03-31 16:59:38 +01:00
Richard van der Hoff
dc5c0928b2 Some basic tests for MessagePanel
Check that it puts the read marker in the right place, and check that the
animation works.

... all of which has been surprisingly painful.
2016-03-31 00:48:46 +01:00
Richard van der Hoff
6069812fcf Create Junit reports from karma 2016-03-29 00:12:59 +01:00
Richard van der Hoff
04561ea6e6 Use phantomjs when running a single test 2016-03-29 00:12:59 +01:00
Richard van der Hoff
5f3b82a767 Stub out the matrix client 2016-03-29 00:12:59 +01:00
Richard van der Hoff
7e1e2347b5 Don't need alias for test-component-index 2016-03-29 00:12:59 +01:00
Richard van der Hoff
e428f48269 Source map working 2016-03-29 00:12:59 +01:00
Richard van der Hoff
c516ecebcc No need for .babelrc 2016-03-29 00:12:59 +01:00
Richard van der Hoff
d7801ef3a4 Vaguely working webpack test 2016-03-29 00:12:59 +01:00
Richard van der Hoff
f60dd93660 Initial implementation of some karma/mocha tests
It does something, but things I don't like:

* it churns for 15 seconds webpacking everything. Do we really need to get
  webpack involved here?

* I don't think there's any way to control which tests get run and which don't.

Other things I'd want to fix up include:

* Make it run on jsdom or phantomjs instead of Chrome
* figure out how to configure babel without a .babelrc
2016-03-29 00:12:58 +01:00