Unable to recognize objects on Chrome browser via UFT 14.02
I am using Chrome 56.0.2924.87 and UFT 14.02
I have installed HPE Functional Testing Agent along with agent crx file item.
The Chrome browser is zoomed to 100%.
Using Object Spy, I am unable to recognize any object in the entire page. Every time, I try to hover over or click, it shows me as:
WinObject: Chrome Legacy Window
Also, If I try to click on record by going to "Record & Run settings → Open the following when recording or running".
I am getting the following error, though:
Unable to Launch browser. The specified browser is not installed
I have followed the following steps to solve my problem:
Set the system display settings to "100%" and resolution "2560 X 1440". Once this done, log out and log in back for the changes to take effect
Zoom the Chrome browser to "100%".
Drag and drop Agent.crx from the Installation/Chrome folder to browser to install the Extension.
Launch UFT and then launch Chrome browser. Use Object Spy, you can now see that objects are being identified.
I had the same problem. UFT had already installed the Agent Extension, but it was disabled. Enabled it from Extensions page. Worked fine.
Check if your Chrome is having the HPE Functional testing Agent through Options → MoreTools → Extensions.
And Enable if it is already installed and in Disable Mode
Open chrome://flags.
Search for "Touch events API" and set it to "Enabled"
Search for "User Activation V2" and set it to "Enabled"
Click the restart chrome prompt.
I am using Firefox 50.0. After auto update of Firefox to version 50.0, Firebug has stopped working and attempting to use it is showing an inbuilt Firefox console while inspecting any DOM element.
Is there any patch to use Firebug on Firefox 50.0 version?
Solve The problem by Changing Mozilla Browser Configuration Settings.
Open A Blank Tab
type about:config in address bar then press enter (click on I accept the risk!)
find browser.tabs.remote.autostart
select the option then click the mouse right side
Turn The Option As False
Close the browser for restart browser
open browser again, inspect the element. I hope It Works Properly.
I manage to get Firebug work again, so here is what I done.
Everyone knows that Firebug isn't being developed or maintained any longer because it can't work with e10s, so here is my workaround:
Download Firefox Developer edition so you can allow XPI installation.
firefox-53.0a2.en-US.win64.installer.exe or
firefox-53.0a2.en-US.win32.installer.exe
Run Firefox developer edition after installing and go to the about:config (type in url bar)
Find xpinstall.signatures.required (set to false)
Find browser.tabs.remote.autostart (set all to false: browser.tabs.remote.autostart.1 and browser.tabs.remote.autostart.2)
NOTE: The Multi-process architecture improves the browser's stability, performance and security by separating tasks into processes, you disabling it at own responsibility.
After that you need to restart the browser.
Now you can go at the Firebug repository and install desired version
Here you can find all Firebug installations
I chose latest firebug-2.0b8.xpi and it forking fine.
P.S. You can disable updates for Firefox Developer edition.
Hope it helps.
Head over to Firebug website, you can see following message:
The Firebug extension isn't being developed or maintained any longer. We invite you to use the Firefox built-in DevTools instead.
Also Sebastianz told me,
Firebug is discontinued. The team has split up, the former team leader Jan "Honza" Odvarko is working on the Firefox DevTools now.
As #Makyen said in his answer, Firebug does not work with multiprocess Firefox, so remove Firebug right now and try Firefox DevTools instead, it's not optional (sadly), unless you don't update Firefox :)
Update 1
Take a look # Why got Firebug removed after updating Firefox to version 50?
Update 2
Take a look # my answer here: how to revert firebug to old version
Firebug does not work with multiprocess Firefox
The Firebug site claims that:
Firebug 2.0.18 is compatible with Firefox 30 – 52
However, it also explains that [emphasis mine]:
Firebug 2.0.18 fixes issue 8030. The extension is marked as multi-process (e10s) compatible so, it isn’t blacklisted and users can continue installing it. This way Firebug can help users to easily migrate into built-in Firefox developer tools – in case it’s running in multi-process enabled browser. When opened in a multi-process Firefox, Firebug’s tools cannot be used. Firebug will then only assist the user with migration to Firefox’s built-in tools.
They also direct you to read: Unifying Firebug & Firefox DevTools
That page says that [emphasis mine]:
Firebug 2 doesn’t work in multi-process browsers (i.e. e10s) and converting it is too complex, so it will stop working when e10s is activated in Firefox. You will be able to disable e10s for a while to keep using Firebug 2, but this won’t last forever.
The fact that Firebug does not actually work in multiprocess Firefox will account for different people having different experiences with Firebug working or not working in a particular version of Firefox. Firefox automatically enabling multiprocess mode will depend on multiple factors, including what other add-ons are installed in the profile.
Using Firebug in newer versions of Firefox
Thus, to use Firebug in newer versions of Firefox, you will need to disable Firefox from entering multiprocess mode. This can be done from the about:preferences page (also available from Tools➞Options). This an option which is under the "General" tab as "Enable multi-process Firefox ...". If multiprocess is not available, this option will not be shown. This option can also be changed by adjusting the preference browser.tabs.remote.autostart from about:config. [Note: browser.tabs.remote.autostart.2 and browser.tabs.remote.autostart.1 also appear to be used to indicate default states, thus I suggest using the about:preferences page to change this option.]
You can determine if your Firefox is currently running in multiprocess mode by looking in about:support. The line "Multiprocess Windows" under "Application Basics" will state if multiprocess is enabled or disabled.
Set up profiles explicitly for testing
Personally, I have different profiles set up for each of multiprocess explicitly disabled and multiprocess explicitly enabled (set browser.tabs.remote.force-enable to true), so I can perform testing under both conditions, with the state of multiprocess being enabled/disabled being known in advance.
I had the same problem when I updated Firefox. I was so addicted to firebug but I moved on to Firefox developer edition - https://www.mozilla.org/en-US/firefox/developer/
It also comes with the firebug theme which resembles firebug UI and its efficient.Just install FDE and activate the firebug theme as shown in the image below :
I had the same unexpected surprise when ubuntu updated FFX and suddenly things like the script panel stopped working. Since I was in the middle of working on something with a short deadline, I was not going to have the luxury of learning the firefox developer toolset and desperately needed to get firebug working. The fix that finally worked for me was to set Firefox preferences not to update. Then download v 49.0.2
https://support.mozilla.org/en-US/kb/install-older-version-of-firefox
I also had to tell Ubuntu not to include firefox in it's upgrades.
It looks like firebug will no longer be maintained as a seperate project, so you will want to get familiar w/ the built in dev tools, but hopefully this buys you some time. Worth mentioning (if I'm reading this right, it sounds like it will be integrated into the native tools:
https://blog.getfirebug.com/2016/06/07/unifying-firebug-firefox-devtools/
https://github.com/firebug/firebug.next
Its working. You need to install one more add-on "Firepicker" and restart the Firefox.
https://addons.mozilla.org/en-US/firefox/addon/firepicker/
I managed to resolve this issue by simply downgrading to mozilla old version using this url:
open https://ftp.mozilla.org/pub/firefox/releases/50.0/win64/en-US/
download and run the .exe setup
Go to Settings - > Add Ons
Click on extensions and search for firebug and firepath and then add those extensions
Hope this should resolve the issue. For those using Windows 32 machine can use the url
https://ftp.mozilla.org/pub/firefox/releases/50.0/win32/en-US/
http://toolsqa.com/selenium-webdriver/xpath-helper/
Open a new tab and navigate to any webpage. I have used www.DemoQA.com for demo.
Hit Ctrl-Shift-X (or Command-Shift-X on OS X), or click the XPath Helper button in the toolbar, to open the XPath Helper console.
Hold down Shift as you mouse over elements on the page. The query box will continuously update to show the XPath query for the element below the mouse pointer, and the results box will show the results for the current query.
If desired, edit the XPath query directly in the console. The results box will immediately reflect your changes.
Repeat step (2) to close the console.
I am using Debian 7 and Chromium browser.
I'm setting up OAuth authentication via google developer console, but for some reason when I enter https://console.developers.google.com, browser starts loading the page, saying "Waiting for console.developers.google.com" and is stuck forever.
Once in ~7 times it eventually loads the page, but then when I click on any tab, it freezes again.
Anyone experienced something like that?
P.S. On Windows everything's fine.
P.P.S The problem is specific for Chromium browser. Chromium also glitches with google+ notifications - they won't load.
you can try loading Google developer console in privacy mode, meaning opening the console from https://cloud.google.com/ in an incognito window.
"If it works there, it means one of your extensions is causing the security problem and you should remove it." as it explained on the Google Chome Help page :'Fix connection errors.' (Your connection is not private > Tip 2: Try opening the page in incognito mode.)
I am creating an add-on for mozilla firefox using Add-on SDK. I have gone through https://developer.mozilla.org/en-US/Add-ons/SDK regarding basics. However, I am now facing an issue with buttons. I want a button to be attached to the navigation toolbar. When I run the main.js file with "cfx run" the button shows up where it should until that firefox window is closed. If I create a .xpi file and open it in firefox it shows the button until we restart the browser. The bottom line is that add-on button vanishes after browser restart. Please, help me regarding this. Thanks in advance. The code is same as given in the mozilla developer tutorials.
Are there any errors? Can you show us some code so we can get a better idea of what you're doing?
To debug this sorts of initialization problems try this:
start the browser
open the browser console, then hit 'clear' to remove existing log entries so you can easily see which ones are caused by the add-on
install the add-on - any errors?
open the add-on manager, disable the add-on, then enable it - any errors?
restart the browser with the add-on installed, then open the browser console. any errors?
Can you reproduce this issue with a simple example add-on, for example this one?
I'm trying to debug my Firefox add-on with Chromebug, but I can't see the error trace or log trace. I've configured a dedicated profile and set about:config parameters according to this Mozilla tutorial. I've installed Firebug and Chromebug with the same version (1.7.2) But when I execute one of my extension "action" with "error thrower" code, nothing happened. No log, no trace.
In Chromebug, the file list is empty. I read in multiple discussions on the web that I should see a list of debuggable scripts.
A screenshot of my environment:
What else must I do?
Update April 2014: The browser debugger is now integrated in the "Browser Toolbox" and you no longer need to set about:config prefs. Just use the developer tools configuration/settings panel: "enable chrome debugging" and "enable remote debugging". The "Browser Toolbox" will then be available in the developer tools panel.
Chromebug has not worked for me for many months. I think it's just been silently abandoned but thankfully on Firefox 19 or later, it's possible to use the built-in JS debugger on the browser itself. Go to about:config and set the following two prefs:
devtools.chrome.enabled: true
devtools.debugger.remote-enabled: true
After you restart the browser, the Web Developer menu will contain a "Browser Debugger" entry.
More info here: https://developer.mozilla.org/en/docs/Debugging_JavaScript
If possible, I'd suggest using Aurora for your debugging because the built-in debugger was a little limited when first launched and keeps getting better with every release.