m (New page: == Overview == The manual testing runner is one type of our internal runners which dedicate to functional testing that are impossible to deliver with automation. It's designed to help de...) |
m |
||
| Line 9: | Line 9: | ||
You could write the manual testing procedures( scripts ) in your preferred language, currently the following language are supported: | You could write the manual testing procedures( scripts ) in your preferred language, currently the following language are supported: | ||
| − | === Trac Wiki === | + | === Trac Wiki === |
| − | Write the scripts inside a <pre> tag at the beginning of doc body indicate the | + | Write the scripts inside a <pre> tag at the beginning of doc body indicate the '''TracWiki format''' is under use: |
| − | <pre> | + | <pre><body> |
| − | </pre> | + | <pre> |
| − | HTML | + | === TC 1 === |
| + | 1. Step1; | ||
| + | 1. Step2; | ||
| + | 1. Step3; | ||
| + | * Expected Result: The output codes of editor should be: | ||
| + | {{{ | ||
| + | Output data... | ||
| + | }}} | ||
| + | * Actual Result: JavaScript error thrown. | ||
| + | </pre> | ||
| + | </body> | ||
| + | </pre> | ||
| + | === HTML === | ||
| − | Write the scripts inside a <div> tag at the beginning of doc body indicate the HTML is under use: | + | Write the scripts inside a <div> tag at the beginning of doc body indicate the '''HTML''' is under use: |
| − | <pre> | + | <pre><body> |
| − | </pre> | + | <div> |
| + | <ol> | ||
| + | <li>Step1;</li> | ||
| + | <li>Step2;</li> | ||
| + | <li>Step3;</li> | ||
| + | </ol> | ||
| + | <ul> | ||
| + | <li>Expected Result: The output codes of editor should be: | ||
| + | <pre> | ||
| + | Output data... | ||
| + | </pre> | ||
| + | </li> | ||
| + | <li>Actual Result: JavaScript error thrown.</li> | ||
| + | </ul> | ||
| + | </div> | ||
| + | </body> | ||
| + | </pre> | ||
| + | == Common Tasks == | ||
| + | |||
| + | === Test Decision === | ||
| + | |||
| + | The most important step is to give a judgment to the test's final result after reproducing the procedures. A ''''PASS'''' button along with a <span style="font-weight: bold;">'</span>'''FAIL'''' button are provided to achieve this. | ||
Revision as of 11:22, 25 September 2009
Contents
[hide]Overview
The manual testing runner is one type of our internal runners which dedicate to functional testing that are impossible to deliver with automation. It's designed to help developers/reports authoring and viewing manual testing scripts with ease, and with the ability to seamlessly integrate with CKTester.
Script Authoring
You could write the manual testing procedures( scripts ) in your preferred language, currently the following language are supported:
Trac Wiki
Write the scripts inside a <pre> tag at the beginning of doc body indicate the TracWiki format is under use:
<body>
<pre>
=== TC 1 ===
1. Step1;
1. Step2;
1. Step3;
* Expected Result: The output codes of editor should be:
{{{
Output data...
}}}
* Actual Result: JavaScript error thrown.
</pre>
</body>
HTML
Write the scripts inside a <div> tag at the beginning of doc body indicate the HTML is under use:
<body> <div> <ol> <li>Step1;</li> <li>Step2;</li> <li>Step3;</li> </ol> <ul> <li>Expected Result: The output codes of editor should be: <pre> Output data... </pre> </li> <li>Actual Result: JavaScript error thrown.</li> </ul> </div> </body>
Common Tasks
Test Decision
The most important step is to give a judgment to the test's final result after reproducing the procedures. A 'PASS' button along with a 'FAIL' button are provided to achieve this.