Service Virtualization

  • Private Community
Back to discussions
Expand all | Collapse all

I'm getting "Exception caught in action :JSONObject["screenjson"] not found" error message  when i importing Selenium script

  • 1.  I'm getting "Exception caught in action :JSONObject["screenjson"] not found" error message  when i importing Selenium script

    Posted May 29, 2017 06:47 AM

    Hi,

     

    I'm getting "Exception caught in action :JSONObject["screenjson"] not found." error, when i'm trying to import selenium json script, after recording a particular step using selenium builder and exporting as JSON. 

     

    How to resolve this? help me.



  • 2.  Re: I'm getting "Exception caught in action :JSONObject["screenjson"] not found" error message  when i importing Selenium script

    Broadcom Employee
    Posted May 30, 2017 05:08 AM

    Hello,

     

    Please mention the exact versions of Firefox, Selenium Builder and DevTest.

    If your JSON script includes "pause" or "saveScreenshot", then this could be one of known issues found recently. Open a new support case giving all details including the JSON script and you may get the fix if it is found to be the same issue.

     

    Regards,

    Javed



  • 3.  Re: I'm getting "Exception caught in action :JSONObject["screenjson"] not found" error message  when i importing Selenium script

    Posted May 30, 2017 07:13 AM

    Hello Javed,

     

    Please find the version details below:

    DevTest: 9.5.1

    Firefox: 45.0.2

    Selenium Builder: 3.1.2

     

    Thanks,

    Prabhu



  • 4.  Re: I'm getting "Exception caught in action :JSONObject["screenjson"] not found" error message  when i importing Selenium script
    Best Answer

    Broadcom Employee
    Posted Jun 08, 2017 10:48 AM

    Hi Prabhu,

     

    Please check if your JSON script includes "pause" or "saveScreenshot", then this could be one of known issues found recently. Open a new support case giving all details including the JSON script and you may get the fix if it is found to be the same issue.

     

    Regards,

    Javed