Forum Discussion

crossan007's avatar
crossan007
New Contributor
6 years ago

SmartBear Test Extension does not work in Chrome 75

When attempting to execute a test using TestExecute, Chrome is launched, and the URL bar displays "chrome-extension://gmhjclgpamdccpomoomknemhmmialaae/exit"; however, the body of the page indicates that the URL could not be loaded.

 

Chrome version: 75.0.3770.100 (Official Build) (64-bit)

SmartBear Test Extension version: 14.0.0

TestExecute Version: 14.10.999.11 x64

 

The specific reason for the failure differs depending on whether I launched Chrome in "incognito" mode, or standard mode.

 

When launched in standard mode, the error message is "ERR_FILE_NOT_FOUND", and the Network log corroborates the claim:

 

When launched in "Incognito" mode, the error is slightly different: "ERR_BLOCKED_BY_CLIENT":

 

I have configured the permissions for the plugin to both "Allow in incognito" and to "Allow access to file URLs":

Blocked
Chrome
Error
plugin
TestExecute
  • crossan007's avatar
    crossan007
    6 years ago

    I've resolved the issue.

     

    The key was this: the screenshots indicated the extension returning a failure to load the `/exit` path.

     

    `/exit` was not the URL under test, but WAS present in my CLI call: &"C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe" E:\Jenkins\workspace\Feature_SmartBearTests\Tests\SmartBearTesting\SmartBearTesting.pjs /run /ns /exit https://TestApp.MyDomain.Com

     

    I was using code in the Startup.JS file to detect the final parameter:

    function ParameterEvent_OnStartTest(Sender)
{
  if(ParamCount() > 0)
  {
    var count = ParamCount();
    var parameter = ParamStr(count - 1);
    Project.Variables.URL = parameter
  }
}

    Howevre, this code was actually returning the penultimate parameter as the URL to test (not the final parametre), since the 0th index of the array is actually the fully qualified path to the invoked executable: https://support.smartbear.com/testcomplete/docs/reference/program-objects/builtin/paramstr.html?q=ParamString()

     

    removing the "-1" from the call to "ParamStr()" returned the desired portion of the CLI parameter set(the URL to test), and therefore directed the browser at my intended URL.