Users Guide"

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

(Initliaze CKTester user's guide)
 
m
Line 1: Line 1:
−
== Overview ==
+
== Overview ==
−
'''CKTester''' is our internal testing hub, created to provide seamless and integrated testing experience to our developers, been capable of managing and interfacing tests from various projects which may potentially rely on different testing frameworks/runners. Been designed with convenient authoring and ease of viewing the test cases in mind, it could be running independently in all situation from a browser : locally, on a web server or via secure connections.
 
  
−
== Installation ==
+
'''CKTester''' is our internal testing hub, created to provide seamless and integrated testing experience to our developers, been capable of managing and interfacing tests from various projects which may potentially rely on different testing frameworks/runners. Been designed with convenient authoring and ease of viewing the test cases in mind, it could be running independently in all situation from a browser : locally, on a web server or via secure connections.
  
−
== Common Tasks ==
+
== Installation  ==
  
−
== History ==
+
Below we'll take the CKEditor project as an example to illustrate the install process:
−
CKTester is evolved from previous project '''FCKTest'''.
+
 
 +
#Checkout CKEditor trunk( or any other version are subjected to test) from [http://svn.fckeditor.net/CKEditor/trunk/ SVN] ( We name the working copy path as CKEDITOR_ROOT below ).
 +
#Checkout CKEditor's testing branch from [http://svn.fckeditor.net/CKEditor/tests/ SVN] ( We name the working copy path as CKEDITOR_TEST_ROOT below ).
 +
#Checkout CKTester from [http://svn.fckeditor.net/CKTester SVN] into a folder( e.g. cktester ) under CKEDITOR_TEST_ROOT( We name the working copy path as CKTESTER_ROOT below ).
 +
#Open the file {CKTESTER_ROOT}/variables.js.tpl with modification to the following variables:
 +
<pre>
 +
</pre>
 +
#<br>
 +
 
 +
== Common Tasks  ==
 +
 
 +
== History ==
 +
 
 +
CKTester is evolved from previous project '''FCKTest'''.  
 +
 
 +
<br>

Revision as of 07:55, 24 September 2009

Overview

CKTester is our internal testing hub, created to provide seamless and integrated testing experience to our developers, been capable of managing and interfacing tests from various projects which may potentially rely on different testing frameworks/runners. Been designed with convenient authoring and ease of viewing the test cases in mind, it could be running independently in all situation from a browser : locally, on a web server or via secure connections.

Installation

Below we'll take the CKEditor project as an example to illustrate the install process:

  1. Checkout CKEditor trunk( or any other version are subjected to test) from SVN ( We name the working copy path as CKEDITOR_ROOT below ).
  2. Checkout CKEditor's testing branch from SVN ( We name the working copy path as CKEDITOR_TEST_ROOT below ).
  3. Checkout CKTester from SVN into a folder( e.g. cktester ) under CKEDITOR_TEST_ROOT( We name the working copy path as CKTESTER_ROOT below ).
  4. Open the file {CKTESTER_ROOT}/variables.js.tpl with modification to the following variables:
 




Common Tasks


History


CKTester is evolved from previous project FCKTest. 









Retrieved from "https://docs-old.ckeditor.com/index.php?title=CKTester/Users_Guide&oldid=2683"