cancel
Showing results for 
Search instead for 
Did you mean: 

SmartBear Test Extension does not work in Chrome 75

SOLVED
Highlighted
New Contributor

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:image.png

 

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

image.png

 

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

image.png

1 ACCEPTED SOLUTION

Accepted Solutions
New Contributor

Re: SmartBear Test Extension does not work in Chrome 75

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=Pa...()

 

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.

5 REPLIES 5
New Contributor

Re: SmartBear Test Extension does not work in Chrome 75

I've also attempted adding the extension to the Chrome whitelist in the registry via "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallWhitelist" as suggested by the KB article at https://smartbear-cc.force.com/portal/KbArticleViewer?name=How-do-I-whitelist-an-extension-in-Chrome...

 

This action did not resolve the issue.

Community Hero

Re: SmartBear Test Extension does not work in Chrome 75

New Contributor

Re: SmartBear Test Extension does not work in Chrome 75

While the docs page you linked (first) indicates no support for Chrome 75, the patches page you linked (second) does indicate that no patches are necessary for Chrome 75.   However, the patches page indicates TestExecute build 1042 is compatible, while I *think* I'm on a previous build (14.0.999.11), and clicking "update" in the application tells me that there are no updates available.

 

Taking a step back, I've uninstalled Chrome 75, and installed Chrome 74.   I'm still seeing the same problem.

Community Hero

Re: SmartBear Test Extension does not work in Chrome 75

Then it's best that you contact Support directly with your question.  Here's the link:

https://support.smartbear.com/testcomplete/

New Contributor

Re: SmartBear Test Extension does not work in Chrome 75

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=Pa...()

 

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.

New Here?
Join us and watch the welcome video:
Watch the New Interview
APITestingMistake#2
Top Kudoed Authors