10 Commits (1df6837649e31dcde0f72458e4568f2331ea126e)

Author	SHA1	Message	Date
Michael Telatynski	8ba54f5f7d	Don't use expect and jest-mock anymore as they're implicit from jest ... Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>	2020-01-18 01:38:22 +00:00
Travis Ralston	54f3288dea	Fix imports for tests ... This doesn't fix the fact that someone called it "peg".	2020-01-09 17:23:27 -07:00
Michael Telatynski	e6d8487302	Fix more tests	2019-12-17 11:47:01 +00:00
Michael Telatynski	6ad31fe023	30 test failures to go :D	2019-12-16 11:12:48 +00:00
Michael Telatynski	18f81d80db	Initial jest stuff. Blocked on Babel 7	2019-12-13 13:43:48 +00:00
Michael Telatynski	d4d51dc61f	Rip out the remainder of Bluebird	2019-11-18 10:03:05 +00:00
Travis Ralston	d20bdbbc1a	Disable room settings tests	2019-01-28 14:11:10 -07:00
Stephen Solka	0bb35944f9	replace expect.createSpy() with jest.fn() ... Signed-off-by: Stephen Solka <stephen0q@gmail.com>	2019-01-02 16:59:48 -06:00
Luke Barnard	d3dc2a33b4	Fix bug preventing setting room power levels ... - don't use refs, use onChange of PowerSelector - store power levels as state in the RoomSetting component	2018-02-28 16:32:20 +00:00
Luke Barnard	d91d1932f4	Add tests for RoomSettings ... For setting: - name - topic - history visibility - power levels Testing RoomSettings required more stubbing on the matrix client. The power level tests should be failing at this commit, with fixes being made in upcoming commits. Some tests are marked as known failures that we should fix but aren't necessarily bugs: - SettingStore.setValue is used when saving despite the user not having made a change. - Testing directory publicity changes cannot be tested because we update state asynchronously in componentWillMount (which we do not block on in beforeEach). Also, we needed to use `export default` to make sure everything uses the same client peg and client.	2018-02-28 16:07:21 +00:00