Manual testing runner

[Garry Yao]

A dedicated type of runner should be added to support manual testing, with the following features:

1. Seamless integration with CKTester, include working with the fort in two modes.
2. Providing a manual testing stage composed of testing target ( a editor instance in case of CKEditor ) along with a pilot panel of testing scripts.
3. Writing scripts with ease by leveraging either HTML or the TracWiki Format to compose testing scripts, this could be as simple as writing the scripts inside the first block right under body( use <pre> for TracWIKI and <div> or other tag for HTML ).

[Garry Yao]

Fixed with [4189] at CKTester and [4190] at CKEditor.

[Garry Yao]

After discussing with Fred, both HTML and Trac Wiki format should be enabled to write scripts, update the description accordingly.

[Garry Yao]

Manual TCs added at :

• ​http://ckeditor.t/tt/4375/1.html for TracWIKI format;
• ​http://ckeditor.t/tt/4375/2.html for HTML format.

[Garry Yao]

Update with [4204] at CKTester and [4205] at CKEditor.

[Tobiasz Cudnik]

From manual writing perspective using wiki text (TracWiki in our situation) is easier and more readable (especially for lists). Important thing to notice here is that we're already using it daily in tickets, so that's noting new for us. Additionally it always gives possibility to parse it to HTML.

This sad, i'm opting for wiki text instead of HTML in this case.