Forum Discussion

SaravanaKumar_N's avatar
SaravanaKumar_N
Contributor
8 years ago

Do we have access for BuiltIn object at Script Extensions

Hi All, My aim is to have a method at our Script Extensions file, that would return the array of command line variables. But it looks like we do not have access for 'BuiltIn' objects at Script Exte...
  • HKosova's avatar
    HKosova
    8 years ago

    BuiltIn.ParamCount and .ParamStr are wrappers over Sys.Process("TestComplete").CommandLine, so you can try parsing the CommandLine string yourself. Just be aware that spaces can be part of an argument value -- if that argument is enclosed in quotes.

     

    If you use both TestComplete and TestExecute, you'll also need to find out what the current test runner is. Maybe try Sys.WaitProcess("TestExecute") first and fall back to TestComplete.

     

    Or go with tristaanogre's suggestion and use config files instead.

tristaanogre's avatar
tristaanogre
Esteemed Contributor
shankar_r wrote:

I used below function store to my command line arguments into a variable.

 

function Store_CommandLine_Parameters()
{
      var count_CL_Parameters = BuiltIn.ParamCount(); 
      var pv_ColumnName = "CL_Parameter";
      Project.Variables.CommandLineParameters.RowCount = count_CL_Parameters + 1;
       
      try
      {
            for(var a = 0 ; a <= count_CL_Parameters ; a++)
            {
                  Project.Variables.CommandLineParameters.$set(pv_ColumnName,a,aqConvert.VarToStr(BuiltIn.ParamStr(a)));
            }
            return true;      
      }
      catch(ex)
      {
            Log.Warning("Error while processing Commandline parameter(s). Error: " + ex.stack);
            return false;
      }         
}

 you can edit and do a formative or conversion in-order to meet your requirement.

The problem is, as the OP notes, the BuiltIn object is not available to be used within a Script extension (reference https://support.smartbear.com/testcomplete/docs/working-with/extending/script/objects-reference/index.html).

 

I'm not sure how else to get commandline parameters for the TestComplete commandline.  I guess the question is, what are you using those commandline parameters for?  One thing you could do is find some other way of  passing that information into TestComplete.  For example, an INI file or XML file that is read as part of the initialization process of a test run using methods in aqFile, aqString, etc.

 

 

HKosova's avatar
HKosova
SmartBear Alumni (Retired)
8 years ago

BuiltIn.ParamCount and .ParamStr are wrappers over Sys.Process("TestComplete").CommandLine, so you can try parsing the CommandLine string yourself. Just be aware that spaces can be part of an argument value -- if that argument is enclosed in quotes.

 

If you use both TestComplete and TestExecute, you'll also need to find out what the current test runner is. Maybe try Sys.WaitProcess("TestExecute") first and fall back to TestComplete.

 

Or go with tristaanogre's suggestion and use config files instead.

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    8 years ago
    HKosova wrote:

    BuiltIn.ParamCount and .ParamStr are wrappers over Sys.Process("TestComplete").CommandLine, so you can try parsing the CommandLine string yourself. Just be aware that spaces can be part of an argument value -- if that argument is enclosed in quotes.

    Ah!  Yes.  And since the Sys object is available in Script Extensions, this would work.  As mentioned, you're going to have to spend some time working with the aqString object to parse out what you're looking for, but that should DEFINITELY be the way to do this.

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      8 years ago

      OK, not in a script extension (yet) but here's a bit of code you can try.  

       

      Assuming a commandline of 

       

      "C:\Program Files (x86)\SmartBear\TestComplete 12\Bin\TestComplete.exe"  "C:\Source\Sandbox\JavaScriptProject\JavaScriptProject.mds" /dataFile="C:\Test 1\Test.XLS"

      The following returns the value of the "dataFile" parameter:

       

      function getTCCommandLineParameter(parameterString) {
    var string = Sys.Process('TestComplete').CommandLine;

 //Setting the list separator to grab a parameter 
          aqString.ListSeparator = '/'; 
          var parameterListLength = aqString.GetListLength(string);
    var foundParameter;
   
    for (var i = 1; i < parameterListLength; i ++) {
        if (aqString.Find(aqString.GetListItem(string, i), parameterString) != -1) {
            foundParameter = aqString.GetListItem(string, i);
            break;
        }    
    }
    if (foundParameter == undefined) {
        throw Error ('Unable to find parameter ' + parameterString);
    }
    //Resetting list separator back to default
    aqString.ListSeparator = '|';
    return aqString.SubString(foundParameter, aqString.Find(foundParameter, '=') + 1, foundParameter.length);
}

function foo() {
    Log.Message(getTCCommandLineParameter('dataFile'));
}