Ghost Inspector tests are failing on running - ghost-inspector

I record test using Ghost Inspector on a website. But when I run the test in Ghost Inspector, one of the buttons is always greyed (only in the test run), and the test fails. Not sure why this is happening. When I record the button is not greyed.
This is the console output in Ghost Inspector:
1788:23079 Uncaught Error: Error in attempt to create DIL instance
with DIL.c…pendency for DIL v8.0+: Invalid Visitor instance.
The same test if recorder and playback using Selenium IDE runs fine
I also tried exporting the failing test from Ghost Inspector as Selenium IDE (new) and opened in Selenium IDE, and test ran successfully


Without seeing the code/test its a bit hard to tell but I'll take a shot in the dark
1) could be ghost inspector test settings. I would go into settings at the top right corner when you are inside your test and look at browser settings. Make sure you're using the browser you want as well as the correct screen size.
2) Could be a timing issue. You might need to add an assertion to let the button load before trying to click that button.
If these don't help let us know a bit more about the test steps as well as the button you are targeting. what is its function and what are the circumstances when its supposed to be disabled.

Related

firebase web app quickstart-js functions sample project gives error when calling functions

I'm new to firebase.
I'm trying to get the web "quickstart-js -> functions" sample web app working.
I copied the sample into my project, got it to compile, and deployed it.
The web UI is fine. Running the functions is failing.
When I put in the two numbers and press the Add Numbers button, I always get:
Error Code: functions/internal
Error Message:internal
Error Details:undefined
I looked at the server logs, and I didn't see any errors.

Was using Firefox and having this problem. On a whim tried it in Chrome. Works fine in Chrome.
Ended up removing the tags around the little forms. Seems like if you put a button in a form and click it, Firefox thinks you're submitting the form, so no firebase goodness happens. Go figure. Faith in firebase restored.

Breakpoint is not hitting ascx.vb page when attached to w3wp.exe process

I am currently trying to debug an ascx.vb page and the breakpoint is not hitting the page.
I am getting this error "The breakpoint will not currently be hit. No symbols have been loaded for this document".
I have been using this project for 2 months and never encountered this error before. I just did a small change on add button save it on chrome could see the change however, when i am debugging getting this issue for the first time.
Steps done:
Attach the breakpoint to the ascx.vb page
click on debug then attach to process as below (highlighted in yellow) :
checks already done:
Project is being run on debug mode
when debugging the symbols are not loaded.. have check Debug windows modules and is as below:
I have tried loading some symbols which created a folder symbolscache but still the debug point did not hit the page.
Is there something wrong in browser/iis or VS.
I was using VS 2017 but the same issue is occurring on VS 2019 professional.
Any help will be highly appreciated.
Thanks.

You can try to disable the "Just My Code" option in the Debug/General settings.
or
Right click the Solution in solution explorer, click "clean solution", this deletes all the compiled and temporary files associated with a solution. do a rebuild of the solution and try to debug again.

remote webdriver: Element is not currently visible and so may not be interacted with

I use JAVA + WebDriver (Thucydides) and Maven.
I'm trying to automate uploading of a file. If I launch test manually from IDE it passes, but when I launch it with Maven on Remote WebDriver the test fails halfway with the error:
net.thucydides.core.webdriver.WebdriverAssertionError: Element is not currently visible and so may not be interacted with
The browser is FireFox.
Thanks.

Look at screenshot in Thucydides report. It seems that your element is really not visible.

Problem with Flex unit testing in IntelliJ

I have some problems running FlexUnit tests in IntelliJ.
Every time I execute test, Internet Explorer (which is not even set as default browser) pops up and blocks unit test, i.e. blocks it as add so I must allow access through that dumb top bar and then another confirmation and then finally test runs. Is there any way to reconfigure it to another browser or to run it some other way so I just hit the Run button on Idea and I can see results right away?
Thank you for help

As you are using Windows have a look at the first comment by Alexander Doroshko in this bug report: http://youtrack.jetbrains.net/issue/IDEA-49795
Current behavior:
if 'Use system default browser' is selected at Settings | Web Browsers | Default Web Browser then swf/html is started in default OS application (either default browser of standalone Flash player)
if default browser is overridden in IDEA then it is always used both for swf/html.
It would be more convenient if standalone Flash player is used for swfs independently of this setting as soon as it is OS default program for sfws.
I recommend to configure the stand alone flashplayer executable for executing unit tests. As you can also see from the report this has been improved in IDEA 10.

Waiting for flash player to connect to debugger

Using Flex Builder 3 :
I have been getting this problem in every single debug launch for past few hours.
I used to get this earlier too, but once in a while, not with every debug launch.
I found out that flex debugger uses a certain 7935 port but I can't figure out
how to change it?

I remember getting this problem a few times. It might have to do with the Flex Profiler (I used to accidentally click that every now and then trying to launch the debugger).
If you start the Profiler and stop it too fast, it will add something to a file in your home directory that it shouldn't.
Check out /path/to/home/mm.cfg on your operating system (on mac, you can open it in textmate with mate ~/mm.cfg). The mm.cfg file stores some information about debugging in Flex
Then in that file, make sure this is the only content:
ErrorReportingEnable=1
TraceOutputFileEnable=1
If there's an extra line (can't remember/find it, something like PreloadSwf=/Users/[username]/Documents/workspace/.metadata/.plugins/com.adobe.flash.profiler/ProfilerAgent.swf?host=localhost&port=9999), delete it.
Let me know if that fixes it.
Lance

Also just make sure you're not using Chrome. Flash Player debugger (at the time of writing this) does not work in Chrome.

This worked for me: right click on a SWF, select "Open with...", choose "Other...", select the Debug player and check the "Always Open With" checkbox.
Mac OSX / FlashBuilder4

Right click your launched flash application, either in the browser or standalone flash player and click on debugger if enabled and change the radio button from localhost to other machine and enter the ip 127.0.0.1 and you are free to debug. I guess the problem maybe from your host file.

Changing the browser from default (chrome) to IE worked for me

Similar to danjp - This started happening to me after a Flash Player automatic update. I simply reinstalled the debug flash players from the Adobe Flash Player download page and everything works as expected.

Make sure there is a swf file with the proper name in your bin-debug directory and that name matches the swf name specified in index.template.html file for the project.
I had replaced index.template.html file by mistake with a similar one from another project. When I tried to debug, I got this "Waiting for flash player to connect to debugger…" status till it timed out.

To me the problem was that internet explorer opened and showed a certification problem, if i didn´t continue this the debugger would show this error. If i continued on ie, no problem happens.

Resources