FilterDebugger is an alternative to Special:AbuseFilter/test with many more features.

• See which part of edit matched the regex
• See which part of the regex matched the edit
• Immediate response as you type; no need to submit anything to a server and wait
• Test any batch size that will fit in memory
• Generate batches from recent changes, older revisions, abuse logs, or local files
• Does not require EFH/EFM access; all the tests are run client-side, so anyone can use it

mw:AbuseFilter's regexes are Perl Compatible Regular Expressions, which have significant differences from JavaScript regular expressions. FilterDebugger attempts to translate regexes where possible, but not all features are supported. Most unsupported regexes will simply give an error, but a few will produce subtly incorrect results.

Add the following line to your common.js:

mw.loader.load("https://en.wikipedia.org/w/index.php?title=User:Suffusion_of_Yellow/FilterDebugger.js&action=raw&ctype=text/javascript"); // Backlink: [[User:Suffusion of Yellow/FilterDebugger.js]]

By default FilterDebugger will store up to 1000 recently visited log entries using your browser's Cache API. If you might ever view a private filter log from a shared computer, also add this to your common.js:

window.FilterDebuggerCacheSize = 0

Otherwise, if you have lots of free disk space, try:

window.FilterDebuggerCacheSize = 25000