Mark Stacey f47cfbbb3e Use strict assertion mode everywhere (#11012) ... The `assert` module has two modes: "Legacy" and "strict". When using strict mode, the "strict" version of each assertion method is implied. Whereas in legacy mode, by default it will use the deprecated, "loose" version of each assertion. We now use strict mode everywhere. A few tests required updates where they were asserting the wrong thing, and it was passing beforehand due to the loose matching.		2021-05-07 17:08:24 -02:30
..
data	remove transactionCategory in favor of more types (#10615)	2021-03-10 14:16:44 -06:00
e2e	Use strict assertion mode everywhere (#11012)	2021-05-07 17:08:24 -02:30
helpers	Update @metamask/controllers to v6.2.1 (#10701)	2021-03-25 17:37:52 -02:30
jest	remove the ui/app and ui/lib folders (#10911)	2021-04-28 14:53:59 -05:00
lib	remove the ui/app and ui/lib folders (#10911)	2021-04-28 14:53:59 -05:00
mocks	Update @metamask/controllers to v6.2.1 (#10701)	2021-03-25 17:37:52 -02:30
stub	colocate tests in flat structure (#10655)	2021-03-16 16:00:08 -05:00
unit-global	Use strict assertion mode everywhere (#11012)	2021-05-07 17:08:24 -02:30
env.js	@metamask/eslint config@5.0.0 (#10358)	2021-02-04 10:15:23 -08:00
setup.js	colocate tests in flat structure (#10655)	2021-03-16 16:00:08 -05:00