Document toolboxDocument toolbox

Debugging Environment Set Up in Eclipse

This page documents the procedure to debug the custom actions added in Qualitia.

  1. The project in which the Custom Actions are written, the TestHarness.java should be written in the same project. Make sure that TestHarness.java is in the default package only. This project must contain the references of the below jar files and any other jar files that may have been used.

    junit-4.8.1.jar
    mysql-connector-java-5.1.6-bin.jar
    log4j-1.2.17.jar
  2. The TestHarness.java should be written as follows:

    Create an array of type String of size 10.
    Step a: If the debugging is to be done for Chrome browser then size of this string array should be 11.
    Step b: Enter the String array with the following information.
    Qualitia Project Name (Do not suffix it with_projectDb) – String
    Qualitia User Name –String
    Qualitia Release Number –String (Default is 7.01)
    Qualitia Build Number –String (Default is 5.01)
    Qualitia Config File path (QualitiaInstallationFolder/Qualitia.exe.config) –String
    Qualitia Reporter Path (QualitiaInstallationFolder/Common/Reporter) –String
    XML Path (Refer the key xmlPath in the Qualitia.exe.config file) –String
    Is Offline – (Set this to false) –String
    Set Selenium browser type
    Is Dry Run – (Set this to false) –String


    If Google Chrome is the browser type then chromedriver path must be given under Qualitia Configuration Settings section.

  3. Call the static method of the callController class. Pass the String Array created in step b.
    For example, callController.main (String Array)
  4. Insert a debug point in the Custom Actions.
  5. Debug the Test Harness in Eclipse. The debug point in the Custom class should be inserted.
  6. Sample TestHarness.java is present at Qualitia installed location: %localappdata%\QualitiaWDClient\app-x.x.x\Help. 

Not finding what you need?