m |
m (→Installation) |
||
| Line 7: | Line 7: | ||
Below we'll take the CKEditor project as an example to illustrate the install process: | Below we'll take the CKEditor project as an example to illustrate the install process: | ||
| − | #Checkout CKEditor | + | #Checkout CKEditor's testing branch from SVN ( We name the working copy path as CKEDITOR_TEST_ROOT below ). <br> |
| − | #Checkout CKEditor | + | #Checkout CKEditor trunk( or any other version are subjected to test ) from [http://svn.fckeditor.net/CKEditor/trunk/ SVN] into a folder ( e.g. ckeditor ) under CKEDITOR_TEST_ROOT ( We name the working copy path as CKEDITOR_ROOT below ).<br> |
| − | #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 ). | + | #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 ). <br> |
| − | #Open the file {CKTESTER_ROOT}/variables.js.tpl with modification to the following variables: | + | #Open the file {CKTESTER_ROOT}/variables.js.tpl with modification to the following variables:<br> |
| − | <pre> | + | <pre> // Absolute path point to the root path of CKEditor project. |
| − | </pre> | + | 'CKEDITOR_ROOT' : '/ckeditor', |
| − | #<br> | + | |
| + | // Point to the root path of CKEditor test branch.( You don't need to alter it if your web server's serving root from CKEDITOR_TEST_ROOT. | ||
| + | 'CKEDITOR_TEST_BRANCH_ROOT' : '/' | ||
| + | </pre> | ||
| + | #At last, run the script {CKTESTER_ROOT}/_dev/gen-profile.bat(.sh) ( you'll need install [http://ant.apache.org/ Apache Ant] ) which helps you to generate the testing profile automatically by scanning the resources within {CKEDITOR_TEST_ROOT}.<br><br>After that, you'll get a file created at {CKTESTER_ROOT}/template.js which looks basically like: | ||
| + | <pre> CKTESTER.fort.getProfile = function () | ||
| + | { | ||
| + | return { | ||
| + | cells : | ||
| + | [ | ||
| + | // Generated cell paths... | ||
| + | ], | ||
| + | cellResolvers : | ||
| + | [ | ||
| + | // Some Default cell resolvers. | ||
| + | ] | ||
| + | }; | ||
| + | }; | ||
| + | |||
| + | </pre> | ||
| + | #It's done, now point your web browser at {CKEDITOR_TEST_ROOT}/index.html, a few pilot links there to kick start you testing.<br> | ||
| + | |||
| + | <br> | ||
== Common Tasks == | == Common Tasks == | ||
Revision as of 08:31, 24 September 2009
Contents
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:
- Checkout CKEditor's testing branch from SVN ( We name the working copy path as CKEDITOR_TEST_ROOT below ).
- Checkout CKEditor trunk( or any other version are subjected to test ) from SVN into a folder ( e.g. ckeditor ) under CKEDITOR_TEST_ROOT ( We name the working copy path as CKEDITOR_ROOT below ).
- Checkout CKTester from 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:
// Absolute path point to the root path of CKEditor project.
'CKEDITOR_ROOT' : '/ckeditor',
// Point to the root path of CKEditor test branch.( You don't need to alter it if your web server's serving root from CKEDITOR_TEST_ROOT.
'CKEDITOR_TEST_BRANCH_ROOT' : '/'
- At last, run the script {CKTESTER_ROOT}/_dev/gen-profile.bat(.sh) ( you'll need install Apache Ant ) which helps you to generate the testing profile automatically by scanning the resources within {CKEDITOR_TEST_ROOT}.
After that, you'll get a file created at {CKTESTER_ROOT}/template.js which looks basically like:
CKTESTER.fort.getProfile = function ()
{
return {
cells :
[
// Generated cell paths...
],
cellResolvers :
[
// Some Default cell resolvers.
]
};
};
- It's done, now point your web browser at {CKEDITOR_TEST_ROOT}/index.html, a few pilot links there to kick start you testing.
Common Tasks
History
CKTester is evolved from previous project FCKTest.