ALM Custom Test Type Developer Guide (12.50 and later)
Deployment: Administrator's Rights Without Side-by-Side support

If your site configuration is such that the users have administrator's rights on the client computers and you do not need to support side-by-side running of different test type versions, follow this procedure.

To set up to download your custom test type files to the clients:

  1. Copy the test type files (the class and controls files you created) into the Extensions\MyTestType directory. Put all of the files in the single, flat directory: Do not place files in subdirectories under Extensions\MyTestType.

  2. Change the extension of *.exe files to *.xxx. For other file types, reverse the letters in the files' extensions—for example, change *.dll to *.lld, *.ocx to *.xco, and so forth.

  3. Digitally sign the files. See Signing Files with Digital Signature.

  4. Create an "ini" file that lists the application files (EXE, DLL, OCX) and gives the locations. If you are adding to an existing set, unpack the CAB described below and edit the existing "ini" file.

    Add a section for each of the files you placed in the Extensions directory. These are the files to be downloaded to client machines.

    The format of the section is:

    [File_000x]
    URLName=<URLName>
    Shortname=<shortname>
    Description=<description>
    Register=Y
    RegisterIsolated = Y
    ProgID=<progID>
  5. Create a CAB file containing the INI file, using the cabarc utility. Use the syntax:
    cabarc -s 6144 n my_test_type.cab my_test_type.ini

  6. Digitally sign the CAB file and place it in the Extensions directory under your application\20qcbin.war directory. See Signing Files with Digital Signature.

  7. The contents of the Extensions directory at the end of this procedure are:
    • A directory under Extensions containing your custom class and control files with the extensions changed as explained above (MyTestType folder).
    • The CAB file containing the INI file that lists the files to download.