We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community. If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub. At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

Manual testing runner

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

Seamless integration with CKTester, include working with the fort in two modes.

Providing a manual testing stage composed of testing target ( a editor instance in case of CKEditor ) along with a pilot panel of testing scripts.

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 ).

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.