QTesterman¶

Windows¶

To run QTesterman under Windows, you’ll first need to install Python 2.x and the PyQt4 library. QTesterman is not compatible with Python 3 for now.

If you don’t have any Python installation yet, you are advised to install Python 2.6.1(or latest 2.6.x version) that you can grab from the official Python site (direct Windows Installer link for Python 2.6.5). Once downloaded, simply run it and install the usual way.

Then, get PyQt4 from Riverbank Computing site. You should get the Windows installer package that matches your Python version, for instance PyQt-Py2.6-gpl-4.7.7-1.exe if you installed a Python 2.6.x. The binary PyQt4 package contains everything needed for QTesterman, in particular the QScintilla2 module. When installing the package, you can limit your installation options to the single “Qt libraries” option, discarding all development tools, documentation, and examples.

Once these dependencies have been installed, you can proceed with the [#RunningtheQTestermanInstaller QTesterman installer execution].

QTesterman has been tested on the following combinations:

• Windows XP SP2 with Python 2.5.4 + PyQt 4.4.3
• Windows Vista SP1 with Python 2.5.4 + PyQt 4.4.3
• Windows 7 with Python 2.6.1 + PyQt 4.4.4

Debian-based Distributions¶

Under Debian and derivatives, you should apt-install the following packages (and their dependencies):

• python-qt4
• python-qscintilla2

QTesterman has been tested on the following distributions, with their standard up-to-date packages:

• Ubuntu 8.10..12.10
• Debian lenny, wheezy

Red-Hat-based Distributions¶

Under Red-Hat and derivatives (CentOS, Fedora, RHES, Mandriva, ...), you should install the following RPM (and their dependencies):

• PyQt4
• ... ?

RHES4/CentOS4 only provides Python 2.3, so it won’t run on them.

Mac OS X¶

If you successfully installed QTesterman under an OS X version, please send me some feedback to complete this section !

Comments¶

The following template

You won't see the following lines.
## This is a single-line comment

#*
While this
is a multi-line
comment
#*

Use \# to escape the pound sign.

will result in:

You won't see the following lines.


Use # to escape the pound sign.

Variable Assignments¶

you can create variables in a template dynamically:

#set($foo = "QTesterman")
Hello $foo World!

Leads to:

Hello QTesterman World!

Variable References¶

You may reference a context variable at any time with a $myvar or ${myvar} syntax.

The available context variables for each plugin are defined below.

My variable: $my_variable
Another variable available in my context: ${another_variable}
Say_${within_a_word}_here

If a reference is not found when applying the template, the template code is unchanged. For instance, with the template above, if my_variable evaluates to 2, within_a_word to "hello", but another_variable is not found, this will produce:

My variable: 2
Another variable available in my context: ${another_variable}
Say_hello_here

To substitude the placeholder with a blank instead of leaving the original template code, use a $my_var syntax:

Missing variable: $!{missing}

Would generate:

Missing variable:

If a variable cannot be evaluated to a string representation, an exception string is injected instead.

Some object referenced by such variables may expose additional properties or methods. In this case, you can access them with a dot-based notation:

This is an object attribute: ${testcase.id}
## Also works without {}:
$testcase.title
## And also with methods
## Assuming $a is a string:
$a.replace('\\n', '<br />')

Actually, you can also reference a call to an exposed function directly. Let’s assume that a function toHtml(s) that escapes the usual HTML characters is provided in the current context:

<p>Description: $toHtml($description)
</p>

Applied with $description that evaluates to "check that 100 > 10,\nthen make sure that the function returns within 10s":

<p>Description: check that 100 &gt; 10,<br />then make sure that the function returns within 10s
</p>

Iteration within a Sequence¶

Some variables are evaluated to a list of items. In this case, you may use the #foreach directive to iterate through them:

#foreach ($testcase in $testcases)
Testcase Identifier: $testcase.id
#end

Conditions¶

A if/elseif/else mechanism is available:

#if ($name)
Test case name: ${name}
#else
Undefined test case name
#end

The usual operators are supported: <, >, <=, >=, ==, =, && (and), || (or), ! (not).

this is#if ($a > 10) large#elseif ($a > 5) medium#else small#end, don't you think ?

Notice how you can mix directives and the normal text to procude the desired output.