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.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

← Previous Change
Ticket History
Next Change →

Changes between Version 3 and Version 4 of Ticket #4375

Timestamp:

Sep 8, 2009, 2:38:04 PM (15 years ago)

Author:

Garry Yao

Comment:

Manual TCs added at :

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

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #4375 – Description

v3	v4
2	2	1. Seamless integration with CKTester, include working with the fort in two modes.
3	3	1. Providing a manual testing stage composed of testing target ( a editor instance in case of CKEditor ) along with a pilot panel of testing scripts.
4		1. Writing scripts with ease by leveraging ~~both~~ '''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 ).
	4	1. 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 ).