Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
In HCL OneTest UI v10.0.2, when I launch Firefox browser for Web UI recording and try to record on the browser, it does not generate any test steps. I do not see any packets being collected in annotation toolbar. I am using Firefox 68 ESR.I am able to record on Chrome but not on firefox.
For recording on browsers, HCL OneTest UI provides the Browser Extensions. When you launch Chrome browser for recording, it allows extension to be applied on the fly during browser launch while same is not true for firefox.
To resolve this, user is required to add HCL OneTest UI – Web UI Extension in the browser & launch the Firefox for Web UI recording in the same profile where extension is installed. You can follow these steps:
Install HCL OneTest UI – Web UI Extension on Firefox browser. The extension “webuirecorder_webext.xpi” can be seen at following directory in Windows OS:
C:\Program Files\HCL\HCLIMShared\plugins\com.ibm.rational.test.rtw.webgui.browextension.firefox_1.2.200.v20190529_2318\WebUIRecorderWebExtension
This location can vary a bit depending on your install location of HCL OneTest UI, please check for the similar location.
You can drag & drop the extension on Firefox browser and allow it to install on Firefox. Now you will see HCL OneTest UI – Web UI Extension has been added to Firefox.
HCL OneTest UI - Web UI Extension for Firefox
You can follow similar steps in Linux and Mac OS.
e.g. In Linux it can be at: /opt/HCL/HCLIMShared/plugins/com.ibm.rational.test.rtw.webgui.browextension.firefox_/WebUIRecorderWebExtension
e.g. In MacOS it can be at: /Applications/HCL/HCLIMShared/plugins/com.ibm.rational.test.rtw.webgui.browextension.firefox_/WebUIRecorderWebExtension
When you start Web UI Recording on the Firefox browser, select the Firefox profile where the extension is installed, like shown below:
HCL OneTest UI - Recorder Wizard To Select Firefox browser in a profile for recording
By default in Firefox ESR release, default-esr is the profile which is used by default by the firefox and most probably user might have applied the extension there. To verify which profile was the one where you have applied the extension, you can launch the firefox and open about:profiles url to view the profile name.
Viewing Firefox Profile in use
Now you should be able to proceed to record Web UI Test on Firefox browser.
Related
I followed all recommended steps for setting up a PWA which can be installed on the user device, following the guideline here: Installable PWAs (MDN):
To make the website installable, it needs the following things in place:
- A web manifest, with the correct fields filled in
- The web site to be served from a secure (HTTPS) domain
- An icon to represent the app on the device
- A service worker registered, to allow the app to work offline (this is required only by Chrome for Android currently)
Still, I don't see the browser-default installation prompt.
How do I find out, why my PWA cannot be installed?
I recommend using Lighthouse, which is an excellent tool for auditing your web app with respect to different categories, including PWA properties. It is also available in Google Chrome in the developer tools (Ctrl-Shift-I / Cmd-Opt-I and select tab Lighthouse).
How do I trigger a PWA audit in Lighthouse (in Google Chrome)?
Choose the category Progressive Web App and then click on Generate report.
Example report
In the example below, you can see that there are some issues present. But the reason, why you don't see the installation prompt is the service worker. Apparently, it isn't registered as expected.
Web app manifest or service worker do not meet the installability requirements
How can I see error messages when running a Chrome packaged app? I've been running the app in the browser and using DevTools but this technique has it's limitations.
If you need to inspect app windows, you can reach them at chrome://inspect/#apps
Or, as Daniel mentions, use the Developer Tool app.
General Chrome Debugging
By opening
chrome://inspect/#apps
you may debug all Apps and Extensions.
You may also like the official Google Chrome Apps & Extensions Developer Tool
Debugging Chrome Extensions
As described in the chrome developer Tutorial you can activate the developer mode within the settings. Afterwards an inspect popup option is avaialbe when you right-click an app-icon.
I need to troubleshoot an issue happening in a webview running within my app. This issue only occurs on Android versions lower or equal to 4.3. My app requires an up to date version of Google Play services.
In order to troubleshoot my webview, I usually can run my app under the Android Emulator (with the latest version of Android), then connect to the web view via Chrome (using chrome://inspect) - the web view appears in Chrome and I'm able to browse the DOM and debug.
To run the app under 4.3, I've created (under AVD) a new device from an existing device definition,
then picked the target Google APIs (Google Inc.) - API Level 18. I've then installed my app, but when trying to run it, I get the error message "This app won't run unless you update Google Play services.". There's an "Update" button on the previous dialog, but nothing happen when clicking on it.
I then tried to debug my issue using Genymotion. I've created a device under 4.3, followed these instructions to flash my device with the latest Google Play services and installed my app. I can now run the app and reproduce the issue within this simulated environment.
The trick now is to be able to connect to the web view from my local Chrome browser. I've enabled remote debugging as described here. Now my device appears in Chrome, but the web view is not showing up in the inspector. Similarly, if I open a new tab under the native browser, it won't show up in the remote inspector. If I open a new tab under Android Chrome though, I can see it showing up under my remote Chrome inspector.
I can see two way moving forward and successfully accessing to the DOM of my webview:
Fixing the "Update" issue under the Android Emulator running 4.3
Or
Connecting to my web view from my Chrome inspector while running the app under Genymotion
Any idea on how to solve one of these two problems?
I have been using weinre for sometimes. it's a pretty good tool to debug webview for android 4.3 and lower. It provides almost same interface as chrome debugger.
All you need to do are:
Install weinre
sudo npm -g install weinre
Client side:
Insert the following code to your webpage <head> section.
Note: it's better to put it at end of <head> section, otherwise there will be some strange errors and debugger won't show up.
<script src="http://<your server ip here>:8081/target/target-script-min.js"></script>
Server side
weinre --boundHost -all- --httpPort 8081
Debugger
open the debugger tool from weinre from your desktop browser:
http://localhost:8081/client/
Finally,
select any target in Targets part and then start debugging.
Remote debugging web views only works on devices with android 4.4 and above.
have a look at this :
https://developer.chrome.com/devtools/docs/remote-debugging
Couple days ago Google Chrome automatically updated from version 31.* to version 32.0.1700.76 m. After that happened it does not show in DevTools network traffic request/responses of "application/msbin1" type anymore. These requests are visible in all other browsers' dev tools (FireFox, IE) and in Fiddler, but not in Chrome. Also Chrome's popup menu in this version is very glitchy.
I don't see the way to downgrade Chrome to previous version. Please help I don't want to uninstall Chrome.
Network traffic does not even show resources (XAP file) a page loads.
Example:
http://www.microsoft.com/silverlight/pixel-shader/demo/
This page loads file SilverlightShaderApp.xap, however dev tools of new Chrome's version never shows it in network tab.
I posted the question here, because it's developers question, not just chrome users.
I reported this issue on google chrome forum as well: here.
Possibly related bugs:
Issue 173844: Developer tools (Network section) don't show response of requests from flash applications
Issue 335502: XMLHttpRequests from Silverlight is not visible in devtools network tab
To avoid the bug, you could downgrade to Chrome 31. A fully offline installer can be downloaded from http://download.oldapps.com/Chrome/31.0.1650.39_chrome_installer.exe.
If you downgrade Chrome, don't forget to disable auto-update. Also, "star" the relevant issues on Chromium's issue tracker so you'll receive email notifications for progress updates. When the issue is fixed, enable auto-update again.
Often, starting a new version of Chrome renders a profile unusable for older Chrome versions ("Your profile can not be used because it is from a newer version of Google Chrome."). When you see such message on start-up, either delete your old profile (don't forget to make a back-up!) (you can also try to delete some files, according to various users, deleting "Web Data" and "Web Data-journal" is sufficient), or launch Chrome with a new profile directory (--user-data-dir=path\to\profile-dir).
For more information on user profiles, see http://www.chromium.org/user-experience/user-data-directory.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Installing GWT plugin in Chrome
I am unable to test my GWT project fast enough without it. And I can't find this plugin at the Chrome web store. Although I could download the plugin, Chrome says it won't deploy a plugin unless downloaded directly from the Chrome web store. Anybody know a solution?
There are two ways to bypass the Chrome store check:
1) Type "chrome://extensions" in the browser address bar to open the Extensions screen, then drag and drop the ".crx" extension file on that window.
2) Launch Chrome from the command-line with the switch "--enable-easy-off-store-extension-install"