Change Details

Special:AbuseFilter/test is great because it lets us make sure that the testing pattern won't cause a mayhem by testing against recent edits. However, in addition to that, it would be useful to have an ability to test against log entries (Special:AbuseLog&wpSearchFilter=...), to make sure that - the testing pattern still catches stuff that was caught before - the testing pattern successfully avoids known false positives Currently, we kinda have the ability to do this already via Special:AbuseFilter/examine/log/..., but we need to do this for each log entry. I believe having a batch test just like Special:AbuseFilter/tes would be very useful.

Special:AbuseFilter/test is great because it lets us make sure that the testing pattern won't cause a mayhem by testing against recent edits. However, in addition to that, it would be useful to have an ability to test against log entries (Special:AbuseLog&wpSearchFilter=...), to make sure that - the testing pattern still catches stuff that was caught before - the testing pattern successfully avoids known false positives Currently, we kinda have the ability to do this already via Special:AbuseFilter/examine/log/..., but we need to do this for each log entry. I believe having a batch test just like Special:AbuseFilter/test would be very useful.

Special:AbuseFilter/test is great because it lets us make sure that the testing pattern won't cause a mayhem by testing against recent edits. However, in addition to that, it would be useful to have an ability to test against log entries (Special:AbuseLog&wpSearchFilter=...), to make sure that - the testing pattern still catches stuff that was caught before - the testing pattern successfully avoids known false positives Currently, we kinda have the ability to do this already via Special:AbuseFilter/examine/log/..., but we need to do this for each log entry. I believe having a batch test just like Special:AbuseFilter/test would be very useful.