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.
Related
whenever I click to inspect a site and open the console...
I see this message:-
MetaMask: MetaMask will soon stop reloading pages on network change.
For more information, see: https://docs.metamask.io/guide/ethereum-provider.html#ethereum-autorefreshonnetworkchange
Set 'ethereum.autoRefreshOnNetworkChange' to 'false' to silence this warning.
MetaMask is not installed in the browser. I am using the Brave browser.
How can I stop this?
Metamask comes included in Brave Browser. Go to main menu -> extensions and you will see "Crypto Wallets" which is the built-in version of Metamask that comes pre-installed in Brave. From that screen, you can disable it by using the switch near the name of the extension.
Edit: I just disabled mine and verified that the warning goes away once disabled.
I've an iMac with OS X Yosemite v.10.10.3. I use Firefox Developer Edition 40.0a2. I've a ZTE Open C (FR version) with Firefox OS; Boot2Gecko 2.1.0.0-prerelease (B2G OS).
What I'd like to do is the following: I've a basic webpage (mostyl HTML, CSS and JS) opened in my browser on my Firefox OS phone. I'd like to get the devtools (Cmd+Shift+i) and be able to edit that webpage with my Firefox Developer Edition browser on my iMac.
I've already tried these things:
Use webIDE.
Follow this potential solution.
Connecting a Firefox OS device.
WebIDE Troubleshooting.
Comment déboguer facilement du web y compris sur tablettes et téléphones—french article.
With webIDE, I can build a new app for Firefox OS (with or without a base theme) and I can use the devtools to inspect the DOM and stuff like that. I just want to achieve the exact same thing but directly on my desktop computer.
Do you have any clue?
Feel free to ask me if you need more piece of informations. ;)
Current status
When I launch the Firefox OS browser app, I can inspect (via the devtools) the homepage (DOM stuff, etc.). But when I load another webpage (Google for example), I can't inspect the DOM. Any idea about that?
I often get this message: http://puu.sh/ir2Ju/32563e51bc.png when I switch to several apps I want to debug.
If I understand correctly, you're trying to connect the Firefox Developer Edition WebIDE on your desktop to a tab that is open on your Firefox OS phone. Something like this?
If that's right, once you connect to your phone in the WebIDE, you should see a list of open browser tabs at the bottom of the "Open App" menu, which is in the top left of the WebIDE panel.
When you connect your phone, you have to accept remote debugging.
Then on the left of the window, you should see a dropdown menu with the apps that you can debug. By default, you can only debug unprivileged applications.
Click on the app, the you want to debug and in the middle of the screen click on the "wrench". It is the button to activate debugging.
Now the complicated part. In order to debug privileged apps such as the web Browser. You have to root your phone and change some preferences. To check that you have a rooted phone. Click on the runtime menu and then runtime info.
If your adb is in root mode, then you can press the button to request higher privileges. You can also do that by hand.
There for more info:
https://developer.mozilla.org/fr/docs/Tools/WebIDE/Running_and_debugging_apps#Unrestricted_app_debugging_%28including_certified_apps.2C_main_process.2C_etc.%29
https://developer.mozilla.org/en-US/Firefox_OS/Using_the_App_Manager#Using_the_B2G_desktop_client
Using a real device
On your computer, enter the following command in Terminal/console to enter your device's filesystem via the shell:
adb shell
Your prompt should change to root#android. Next, stop B2G running using the following command:
stop b2g
Navigate to the following directory:
cd /data/b2g/mozilla/*.default/
Here, update the prefs.js file with the following line:
echo 'user_pref("devtools.debugger.forbid-certified-apps", false);' >> prefs.js
After you've finished editing and saving the file, start B2G again using the following command:
start b2g
Exit the android filesystem using the exit command; this will return you to your normal terminal prompt.
Next, reconnect to the App Manager and you should see certified apps appear for debugging.
When this is done, you should see the application "Browser" in the list of available apps for debugging. At the same time, you should see all other application of your phone available as debugging.
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.
I'm looking into chrome frame and I'm wondering how it works.... http://scriptsrc.net shows that it's a javascript that can be embedded on the page....
http://code.google.com/chrome/chromeframe/ shows it as an install file... does the JS prompt for an installation or something?
Google chrome frame is a plugin (think Adobe Flash) for Internet Explorer, that replaces core modules of IE (unlike Flash), like layout/rendering and javascript. But the UI remains. Then there is some javascript that can detect if this is real IE or IE+Chrome, and also offer an install option to the user. Also there is a HTTP-header and a meta-tag that are required to switch IE to chrome mode, when available.
The JavaScript is to detect it and enable it if it's there. (scriptsrc is just giving you the link to the file, which is on the Google CDN.) The end user does have to do a one-time install of it, it's a plug-in (like Flash or Java). Quoting from this page in the Google documentation:
In Internet Explorer, check() determines if Chrome Frame is installed. If not, the user is prompted to install it.