Forum Discussion

simonaferrara's avatar
simonaferrara
Frequent Contributor
2 months ago

General Exception raised within Run Browser action

Hi all,

I'm falling in an random error for which I'm not able to find the root cause nor a workaround.

I'm using TestComplete/TestExecute 15.66.7.7 version.

The automation test is simply opening an Edge browser instance and navigating to the needed url; then, the needed validation web test steps are executed. Within this simple operation sometimes the Test Execute falls in an exception, for which the log doesn't provide so much information. The message is "Exception occured". From the picture, I can see that the browser is still loading the page. That is: it seems that TestExecute is not waiting for the complete loading of the page for the navigation.

The strange thing is that, as you can see from the log below, the test is next correctly executed (the browser interactions are correctly done) but, for that strange Exception, the automated test is marked as failed (by providing a wrong information, since the needed validations are actually passed). 

I'm simply using the Run Browser action to open browser and navigate to the needed url (saved within a project variable):


Please see the generated log below for more details. 

Could you suggest me a way to prevent this exception or the possible root causes for it?

 

web testing
  • rraghvani's avatar
    rraghvani
    Champion Level 3
    2 months ago

    Can you change Sys.Browser("edge").Page("") to Sys.Browser("edge").Page("*") or provide the URL with wildcard e.g. Sys.Browser("edge").Page("https://www.w3schools.com/*")

  • Hassan_Ballan's avatar
    Hassan_Ballan
    Contributor
    2 months ago

    Hello,

    To help you isolate and make sense of it, may I suggest you split the operation to:

    1. Run browser
    2. Navigate to hardcoded URL, and later change to variable
    3. Wait for page to load

    If it is still a mystery, I suggest you contact support.

  • simonaferrara's avatar
    simonaferrara
    Frequent Contributor
    2 months ago

    rraghvaniHassan_Ballan  I'm using the Run browser action through the Keyword Test, and I'm using the url as input parameter. In this way, the code writing is simpler.

    Currently this issue is appearing randomically on both latest 129 Edge version and also a previous one 126.

    Do you think that the Run browser action contains a bug so that it cannot be used anymore and it needs to be implemented through a specific script function by splitting the operations that that action execute? 

    It seems to me that, if there is this need, it is for a workaround of a bug on Run browser action.

    Regards,

    Simona

    • DBowerman's avatar
      DBowerman
      Occasional Contributor
      31 days ago

      I have been dealing with this same issue for quite some time with our Web-based pipelines.  With each new TC/TE release, the issue gets worse. 

      I currently have a case open with SmartBear/TestComplete and they cannot figure it out.  I have suggested that they look into the Run Browser process for a bug.  Here is my process for launching my site using Chrome.  I had to separate out the process of launching the browser from entering my URL because of the Exception error.  It worked for a while, but now I keep getting more and more random Exception errors. 

      We run TE on a VM.  I have noticed that when the exception errors occur, there is aways a "TestComplete Chrome Host (32 bit)" process hung in the Task Manager so that's why I think it's related to the Run Browser process.  I've reported this as well, but again they have not found a solution.  

      We are running TE version 15.68 and Chrome version 129.0.6668.101 (our IT dept controls Chrome updates so we cannot downgrade)

  • simonaferrara's avatar
    simonaferrara
    Frequent Contributor
    11 days ago

    DBowermangood to know that you've raising the same issues and that you've got an opened ticket also.

    I've got an open ticket also on my side, but technician has still not provided a solution for me.

    My perception is the same, that is: a bug within the Run Browser action.

    I'm using latest version of TE (15.68) and latest version of Edge (130).

    Let's synchronize if one of us has got news to resolve the issue, thanks!

    Simona