Daimona Eaytoy 62adeb3ce5 Add a lot of selenium tests for the editing view ... The editing view is currently full of tech debt, brittle and surprising code and whatnot. It's basically a miracle if it works without problem, and it'd be an even bigger miracle if you could change something there without breaking anything. For these reasons, and because that class must be refactored as part of the upcoming overhaul, this patch adds a bunch of selenium tests to test the main functionality of that page. In particular, these tests cover all possible cases (each corresponding to a data source) for which buildFilterEditor can be called, which FTR are: 1 - View the result of importing a filter 2 - Create a new filter 3 - Load the current version of an existing filter 4 - Load an old version of an existing filter 5 - Show the user input again if saving fails after one of the steps above Having automated tests to cover these cases means that we don't have to manually test all the scenarios manually each time the class is touched. Bug: T201193 Change-Id: I408e0a132905416effe0d6d6dc0921991edd66bd		2020-09-29 14:22:53 +00:00
..
ve-abusefilter	VE: Add explicit dependency on targetLoader	2020-06-30 22:47:18 +01:00
ext.abuseFilter.css	Add a lot of selenium tests for the editing view	2020-09-29 14:22:53 +00:00
ext.abuseFilter.edit.js	Add a lot of selenium tests for the editing view	2020-09-29 14:22:53 +00:00
ext.abuseFilter.examine.js	eslint: Update to eslint-config-wikimedia 0.16.0	2020-06-08 21:17:50 -04:00
ext.abuseFilter.tools.js	ViewTools: hide the result box when empty	2020-09-19 12:37:06 +00:00
mode-abusefilter.js	build: Update npm dependencies	2019-07-31 17:29:00 +00:00
red_x.png	Compress PNGs with zopflipng	2016-02-20 20:17:20 +00:00
yes_check.png	Compress PNGs with zopflipng	2016-02-21 00:51:11 +00:00