AgileTestware

Project Configuration

Dragonfly project configuration properties reference.

Overview

Dragonfly configuration is set per ReadyAPI project using project-level custom properties. Initialize properties by right-clicking your project and selecting "Dragonfly: (Un)Initialize project".

Properties like QC_TestPlanDirectory, QC_TestLabDirectory, and QC_TestSet can also be set at the test suite level. Suite-level values take precedence over project-level values — useful when mapping each suite to a different TestPlan/TestLab location.

Configuration Properties

PropertyRequiredDescriptionSample Value
QC_URLYesHP ALM URL. Must end with /qcbinhttp://alm.example.com:8080/qcbin
QC_DomainYesHP ALM domain nameDEFAULT
QC_ProjectYesHP ALM project namedemo-project
QC_userYesHP ALM username with TestPlan/TestLab permissionsjsmith
QC_passwordYesHP ALM password (encrypted and masked automatically)
QC_TestPlanDirectoryYesALM Test Plan path. Created automatically if it doesn't exist.Subject\testplan01
QC_TestLabDirectoryYesALM Test Lab path. Results saved here. Created if it doesn't exist.Root\testlab01
QC_TestSetYesALM test set name. Created if it doesn't exist.myTestSet01
QC_soapUI_ARGSNoExtra testrunner.bat arguments for CI or ALM-launched runs"-j" "-fC:\Reports"
QC_BulkUpdateNoBatch all status updates at end of run for speed.enabled / disabled
QC_RunNameNoOverride the default run name (default: Run: <timestamp> syncing complete)release-1.6-run
QC_ProjectPathNoReadyAPI project path on ALM host machines. Use when running tests from ALM on remote hosts.C:\ReadyAPI-projects\
QC_soapUIPathNoPath to testrunner.bat on ALM hosts (if ReadyAPI is not in the default location)D:\ReadyAPI\bin\testrunner.bat
QC_Export_Disabled_TestsNoExport disabled tests to ALM as wellenabled / disabled
QC_Dragonfly_PluginNoEnable or disable the plugin globallyenabled / disabled
QC_Override_Test_RunsNoRemove all previous runs so each test has only one runenabled / disabled

Custom User Fields

Many ALM setups define custom user fields on Test, TestSet, and Run entities. Dragonfly provides a configuration wizard to map these fields.

ALM Custom Fields Example

ALM custom user fields

Opening the Custom Fields Wizard

If an ALM project has required user properties that have not been mapped in the wizard, you will see errors in the Dragonfly log during most operations.

Custom fields error

Right-click your project and select Dragonfly: Configure Custom Fields to open the wizard:

Custom fields configuration wizard

The wizard lets you configure Test, TestSet, and Run entities. Specify the ALM Field Name, Label, and default value for each, then click Save:

Save custom fields configuration

Once saved, default values are added to the ReadyAPI project:

  • Test → ReadyAPI TestCase custom property
  • TestSet → ReadyAPI project and test suite custom property
  • Run → ReadyAPI TestCase custom property

TestCase custom properties example

Copying Configuration to Other Projects

To reuse the same custom field mapping across multiple ReadyAPI projects:

  1. Right-click any project → Dragonfly: Configure Custom Fields
  2. Select Menu → Copy from project

Copy configuration from project menu

  1. Select the source project and click OK

Select source project

  1. Click Save to apply

Import/Export Configuration

Custom field configuration can be exported to a file and shared with colleagues:

  • Export: Right-click project → Configure Custom Fields → Menu → Export → enter filename
  • Import: Right-click project → Configure Custom Fields → Menu → Import → select file → click Save

On this page