KD Executor is a multi-purpose tool, running on all platform supported by Qt (Windows, Mac, Unix/Linux), which two main purposes are Automatic Testing and automatic demonstration or Presentation of your applications. You can use KD Executor in two different ways:

• For most users who use KD Executor for testing, the KD Executor Shell (presented below) is most convenient.
• More advanced users who already have a test environment in place can also use KD Executor as an advanced record and playback engine, using and configuring KD Executor from the command line.
• See a Quick Tour at our American Distributor's site

KD Executor Shell

The KD Executor Shell Main Window gives an overview about all test suites, test cases and test runs gathered in one table. A result table, is hidden behind the "Result" tab. It contains all performed test ordered and collected by date and time when the execution took place.

Detailled Results shows more information about a certain test result. It displays the different test aspects, and whether the test case failed or passed each one of those.Stdout and Stderr shows the standard output and standard error data from the tested application, which can be good to have when it comes to debugging.

All information about test suites and tests are presented in a tree view. The user may add, edit or remove test suites, tests and test runs. You may Create or Import a Test Suite by Right Clicking in to the Test Suite Table view, which will display the appropriate dialogs for those actions.

Moreover KD Executor Shell make it a simple task for the user to act upon the Test Suite Table items by providing for each of them a context menu which let you interact with them.

The Test Suite Table items are classified in several categories upon which the user can interact easely on a flexible way. Let us go through the main features available ( You may download the KD Executor Programmer's Manual which provides in-depth information [3.7 MB]). :

Test Suite items

• You may create a New Test Suite as a child of an existing Test suite, which gives the user all flexibility to classify a given test plan per area or categories within the tested apllication (e.g GUI testing - backend - etc....).
• The information concerning a Test Suite, may be edited in a dialog which present you all the details for the selected Test Suite.
• The user has the possibility to remove a Test Suite and all its children as well as the result informations by a simple click on the Delete Test Suite action.
• KD Executor Shell gives you the ability to export (for future use or for use on another station/platform) or import Test Suites.
• Creating or editing a Test Suite is made simple, KD Executor Shell displays a dialog wich let you configure the new Test Suite (or change the configuration for an existing one).

Test Case items

• As for the Test Suite items you may Create, Edit, Export or Import a Test Case item.
• The user can also display the property editor related to this test case in a dialog with all information about this particular Test Case.

Test Run items

• This item lets you overview the result of a particular Test. This result may be removed or edited as for the other items.
• Moreover KD Executor Shell let us display the Manual Image Compare dialog, giving us the option to study every undetermined screenshot, and act upon it by changing its status.
• The Use a new property base line... action lets you set the values of this test run to be the new baseline in the following test runs, which means that all property values gathered during the following test will be compared to the property values of this test run.
• KD Executor Shell also gives us the ability to Use a new screenshot base line...following the same principle as described above for the property base line.

The test run table contains all test runs that have been performed during the current program session, stored in a tree view, and ordered in ascending time order.

KD Executor Shell lets you the possibility to delete a Test Run but also to Export it to HTML format.Exporting the test run to HTML will give you a report of all test results in that particular test run, with detailed reasons for it failing, if that occurred.You could for example, publish this file on your Intranet...

Under each date there are one or more test runs. Right-clicking one of them brings up the same context menu as in the Test Run Item section above.

When you select one of the test results in this table or in the test suite table, there will be a more detailed report in the bottom of the main window.

All the operations described above as well as more actions are of course available from the main menu and the toolbar (described in details in the Programmer's manual delivered with our product KD Executor Programmer's Manual [3.7 MB]).
KD Executor Shell gives us for example the ability to run on a single click:

• All test cases in all test suites.
• The selected test cases.
• The currently marked test case.

The Test Suite Dialog is shown when you create a new test suite or edit an already existing one. It contains general information about which application to test, and other settings. All of those are described in details in the Programmer's manual.

The user have the possibility among others to pass parameters to the application being tested, or specify a command to be executed before or/and after the actual application.

You may also specify whether you would like to use exit codes to determine if the test cases failed or not, or configure the Record/Play back engine for this particular Test Suite etc...

The Test Dialog is displayed when you create/edit your test cases. It is possible to create a test case from a file that already exists.This dialog let you enter the information and configuration parameters for this particular test case (the Test Suite it belongs to, the test name, etc....).

KD Executor Shell lets you enter a description of the test case that will be shown as a tool tip in the Test table, as well as in the HTML export..The user may give/select the file name in which the test case shall be saved to and define if she wants to Record and compare Properties and/or ScreenShot. If any properties taken during recording mismatches the one taken during playback the test case will be considered failed.

On screenshot mismatches you can also choose whether you want to have the test case fail automatically, or if you want to compare the screenshots manually. The user can also configure the record/playback engine configuration for this particular test case among other possibilities...

If the user choose to view the Property Editor of a Test Case or a Test Result, the property editor is displayed as shown below:

Listed in the Property Editor are all properties picked during the script recording.

The only differences between the Property dialog for a Test Case and the one for a Test Result is that the the last one also shows the actual value of the property, captured during playback.

An Option dialog is accessible from KD Executor Shell main menu. This dialog allows you to load your last test setup the next time you launch KD Executor.

The user may also edit a script window integrated to the main dialog. This window contains the actual XML script of the currently selected test case. This is intended for advanced users that want to make manual adjustments to a test script while working on it.

In-depth information are available for downloading in the KD Executor Programmer's Manual [3.7 MB].

• Evaluate to try it by yourself.
• See a Quick Tour at our American Distributor's site

Required Qt Versions

KD Executor is supported for Qt 3.2.0 and higher. Qt 2.x versions will definitely not work. KD Executor does not work with the Professional Edition of Qt (due to the lacking XML support in this version).

Licensing and Pricing

To evaluate or purchase KD Executor:

If you are located in the US, Canada, or Mexico, please contact our North American reseller ICS to require an evaluation version or for purchasing information.

Other customers may get an evaluation version by following this link: KD Executor evaluation version... or contact our sales department at sales@kdab.net for purchasing information.

top of the page

Bulk Rates for Field Testing and Demos

1. Internal testing. In this case, normally only comparatively few people use KD Executor extensively. This is where the above developer licenses apply.
2. Enhancing your software. You may want to record auto-running demos of your software and ship them to your customers, or ship KD Executor-enabled versions of your software to your customers so that your customers can send you the generated scripts back when they have found a defect in your software.

top of the page

How To Decide Which License You Need

• Acme Corp. wants to use KD Executor to ship demo versions of their products to 15000 customers. They purchase two bundles à 10000 record/playback-only licenses plus (depending on the number of developers working on the project) one developer license. Without the developer license, they would not be permitted to build KD Executor into their products.
• FooBar Inc. uses KD Executor for inhouse testing with six developers. They purchase six developer licenses.
• NoBugs Software Ltd. uses KD Executor for inhouse testing with two developers and wants to send out a KD Executor-enabled version of their software to 65 customers to let customers record defect situations. They purchase two developer licenses and one bundle with 100 record/playback-only licenses.

How to order KD Executor:

• Download the order form as a PDF File, print it out, fill in the blanks, sign it and fax it to: +46-563-540028
• As soon as we receive your order, we will send a confirmation e-mail with information about where to download the commercial version and how to get support and future updates. We will send you the invoice and, after we have received your payment, the license certificate by postal mail.
• To speed things up, you can wire your payment before you have received the invoice.
• We prefer wire transfers as the most convenient and safest way for all sides. If you'd rather pay by check, please add EUR 25 to cover our banking fees. You can also pay by credit card, contact our sales department for further information.
• If you need quotations, etc. for your internal purchase procedures, please contact sales@kdab.net and we'll be happy to help you.

KD Executor Kickstart

If you purchase 30 or more licenses, you will get a Kickstart day for free, all we will charge you are the instructor's travel expenses. If you purchase 60 or more licenses, we will even cover those. For other pricing, including bundle deals with license sales, please contact us at sales@kdab.net.