Sergio Scabuzzo

When running a an audit on a website (yours, a competiror, or client), you can often find yourself going to around ten or more websites to run tests (Inquiries). 
At each of these you then paste the same URL and run it’s test and repeat for each one. Most of these services use the GET HTTP request method. You see these as the ?q= part in <a href="https://duckduckgo.com/?q=ecotechie" rel="nofollow ugc">https://duckduckgo.com/?q=ecotechie</a>.
I decided to write this plugin so I could input a URL once and run all of these tests more easily. No need to hunt down the website addressses or even leave the WordPress admin dashboard!
Features:
<ul>
<li>Use any valid URL for testing, it doesn’t have to be the current site the plugin is installed on.</li>
<li>Add or remove websites to use for tests (Inquirers).</li>
<li>Sortable by filter types like SEO, Speed, Security, etc. Or create your own tags…</li>
</ul>

Inquirer

Run queries of an arbitrary URL on websites that can take these as query parameters.

Alley

Matthew Boynes

This plugin provides a simple interface for testing your custom rewrite rules.
The purpose of this plugin is to be able to test your own rewrite rules, so 
you’re probably most interested in knowing how to do that, right? The plugin 
provides a filter, <code>rewrite_testing_tests</code> to add your own tests. That filter 
passes an associative array of name => tests. The tests array is an associative 
array of URI => expected match. In the outer array, the “name” is arbitrary and 
for your own reference. In the inner array, the “URI” is the path you want to 
test, and the “expected match” is what WordPress should find as a rewrite 
match.
Enough chit-chat, here’s an example:
<pre><code>function my_rewrite_tests( $tests ) {
 return array(
 'Events' => array(
 '/event/super-bowl/' => 'index.php?event=$matches[1]',
 '/event/super-bowl/page/2/' => 'index.php?event=$matches[1]&paged=$matches[2]'
 )
 );
}
add_filter( 'rewrite_testing_tests', 'my_rewrite_tests' );
</code></pre>
You can see the <code>test_cases()</code> method for a full suite of tests for the “Day 
and Name” permalink structure. It’s not necessary to leave these in (in fact, 
the above demo would wipe them out), unless you want to make sure that your 
custom rewrites aren’t affecting core rewrites. If you aren’t using “Day and 
Name” permalinks, you’ll need to adjust the tests to fit your permalink 
structure.
<h3>Todo</h3>
<ul>
<li>Add a debug bar extension which reads a transient; the transient would be 
updated whenever rewrite rules are flushed. The debug bar extension would 
show pass/fail status and link directly to the settings page.</li>
<li>Add tests for other permalink structures?</li>
<li>Add a way to run this as part of phpunit</li>
</ul>

Rewrite Rule Testing

Regex and WordPress rewrite rules are probably my two Least Favourite Things, so this plugin is essential for making sure I haven't messed anything up :)



Nice

Unit test your rewrite rules from the WordPress Admin.

Inquirer vs Rewrite Rule Testing