Here is a short description of the plugin.  This should be no more than 150 characters.  No markup here please.

Dion Hulse

Mr Tèstøry (dd128)

For best README.md support, the fields under the plugin title, Contributors.. Tags.. etc, should be in a similar format to this readme example. This means that there should be no characters after the : other than the value, no formatting, just a value and new line.
This is the long description. No limit, and you can use Markdown (as well as in the following sections).
For backwards compatibility, if this section is missing, the full length of the short description will be used, and 
Markdown parsed.
A few notes about the sections above:
<ul>
<li>“Contributors” is a comma separated list of wp.org/wp-plugins.org usernames</li>
<li>“Tags” is a comma separated list of tags that apply to the plugin</li>
<li>“Requires at least” is the lowest version that the plugin will work on</li>
<li>“Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on 
higher versions… this is just the highest one you’ve verified.</li>
<li>
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use <code>/trunk/</code> for 
stable.
Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so 
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that’ll be used 
for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code> 
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in 
your in-development version, without having that information incorrectly disclosed about the current stable version 
that lacks those changes — as long as the trunk’s <code>readme.txt</code> points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where 
you put the stable version, in order to eliminate any doubt.
</li>
</ul>
Testing out some Markdown bugs: 
Examples: 
 define( ‘TC_PRE’, ‘Theme Review:[[br]] 
 – Themes should be reviewed using “define(\’WP_DEBUG\’, true);” in wp-config.php[[br]] 
 – Themes should be reviewed using the test data from the Theme Checklists (TC) 
 —– 
 ‘ );
<pre><code>define( 'TC_POST', 'Feel free to make use of the contact details below if you have any questions,
comments, or feedback:[[br]]
[[br]]
* Leave a comment on this ticket[[br]]
* Send an email to the Theme Review email list[[br]]
* Use the #wordpress-themes IRC channel on Freenode.' );
</code></pre>
three backtics: 
 <code>add_action( 'init', function() { 
 // do stuff 
} );</code>
or indents 
 add_action( ‘init’, function() { 
 // do stuff 
 } );
<h3>Arbitrary section</h3>
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated 
plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or 
“installation.” Arbitrary sections will be shown below the built-in sections outlined above.
<h3>A brief Markdown Example</h3>
Ordered list:
<ol>
<li>Some feature</li>
<li>Another feature</li>
<li>Something else about the plugin</li>
</ol>
Unordered list:
<ul>
<li>something</li>
<li>something else</li>
<li>third thing</li>
</ul>
Here’s a link to <a href="https://wordpress.org/" title="Your favorite software" rel="ugc">WordPress</a> and one to <a href="http://daringfireball.net/projects/markdown/syntax" title="Markdown is what the parser uses to process much of the readme file" rel="nofollow ugc">Markdown’s Syntax Documentation</a>. 
Titles are optional, naturally.
Markdown uses email style notation for blockquotes and I’ve been told:
<blockquote>
Asterisks for emphasis. Double it up for strong.
</blockquote>
<pre><code><?php code(); // goes in backticks ?>
</code></pre>

Test Plugin 3 – Testing plugin

This is a great plugin for testing reviews. Edited to 1.

Amazing!

I will change the rating to 5 stars if you can fix this little issue I have with it.

I like it but....

Unforgettable

Apart from the incorrect form title this is one amazing plugin for this reason I'm only giving it 4 stars ;)

Edit: I've removed another star marking this review down to 3 stars, I came here to edit the version of WordPress I'm using, 4.6.1 is not correct, I'm using /trunk but I cannot change from 4.6.1 to the original optional version that was available when first submitting a review.

Edit2: I've removed another star this time because when I submitted my original review I checked the checkbox "Notify me of follow-up replies via email" but looking to the left in the sidebar I see that I am not subscribed this review. During this edit I have the option to once again select the checkbox "Notify me of follow-up replies via email" which I will now check before hitting submit.

Edit3: I am still not subscribed, I've also removed another star because in the sidebar to the left is "Topic Info" it should read "Review Info", also "Topic Tags" should be "Review Tags"

Edit4: I cannot remove any more stars, i.e. I cannot change this to 0 stars, this is a good thing, adding a star back to make this 2 stars again :)

Edit5: Removed that star as when not logged in underneath my review I see "You must be logged in to reply to this topic.", this should read "You must be logged in to reply to this review."

Edit6: Changing my review back to 5 stars because all this is, bugs and all is still AWESOME :)

Alternatives to Test Plugin 3 – Testing plugin

Top alternatives