I would like to run Cypress with the terminal using the Command Line.
However the Chrome I'm running run is set to English.
Which is really odd because when I run the test with the Cypress runner it's run in the native language of my Chrome.
How can I do to set the correct language ?
What I tried so far is :
cypress run --browser chrome -e --LANG=fr-FR
What can I do to set the Chrome in the needed language?
Related
I am using VSCODE on mac and trying to run a debugger to stop at breakpoints, when running an NPM script.
The NPM script is a shell script (.sh) and it starts a "watcher" on 4 different repos, that form my local server for the project.
The issue is that when I run the debugger on the relevant NPM script (using vscode's 'debug script' option), it seems like VSCODE has a debugger attached, but it never stops at my breakpoints.
The server itself seems to work fine.
I read a lot of answers regarding debugging NPM scripts, but they always refer to a .js file.
Am I not connecting the debugger in the correct way?
Is it possible to debug a shell script that runs this way?
My guess is that the debugger is only connected to the shell script which works fine, but "doesn't know" about the breakpoints in the actual repos that are launched with the script.
Would appreciate any help.
Thank you.
I have questions about cypress and BrowserStack
Will anyone have any idea how can I use the argument of --browser in browserstack-cypress run --
browser Chrome#latest: Windows 10, Firefox#latest-1:OS X Catalina command. But this command is not working, I got the error in error: Build creation failed. Error: Chrome latest on Windows is not supported in BrowserStack. See the list of supported browser versions and OS here: https://www.browserstack.com/docs/automate/cypress/browsers-and-os
Not sure why it will be that. Will anyone can help me with this? I will very appreciate it.
Office doc of BrowserStack for the BrowserStack-cypress run command.
https://www.browserstack.com/docs/automate/cypress/cli-reference#generate-configuration-file
Try using
browserstack-cypress run --browser chrome#latest:"Windows 10",firefox#latest-1:"OS X Catalina"
I've tried to debug like descript in docu:
Windows with cmd.exeset PWDEBUG=consolenpm run test
Windows with PowerShell$env:PWDEBUG="console"npm run test
Therefore I've tried in ubuntu:
PWDEBUG=console npm run test
This also doesn't work.
How is the right way to debug in Windows 10?
Next, I've tried the following command in ubuntu:
PWDEBUG=1 npx playwright test
This worked in Ubuntu but not in Windows 10
If you're using visual studio code the default terminal is powershell.
You can open this by going to menu bar: Terminal > New Terminal
If you're not using VS code, just open a new powershell window from the start menu.
You'll know it's powershell as the terminal line start with "PS".
You need to kick off the debugger with two lines. One to turn on the debugger and one to run the tests:
$env:PWDEBUG=1
npx playwright test --headed --browser=chromium
That second lines runs everything as I create this folder with just 1 test file. Refer to the CLI if you want to run a specific tests
VS Code with the terminal window looks like this:
When you run the second line that opens the playwright inspector to allow you to debug:
one liner works for me from VSCode terminal:
set $env:PWDEBUG=1 && npx playwright test --headed --browser=chromium
I followed Vojta's video about how to do debug angularjs in Webstorm.
http://www.youtube.com/watch?v=MVw8N3hTfCI&feature=plcp
However, every time I stop the testacular server in webstorm. I have to reinstall the webstorm debug extension for chrome. Am I doing something wrong? Do I need to install it into some Chrome profile or something?
Seems to be working OK this morning. I think I was running testacular from the command line as well, which was using up the default port of 9876 and was giving me unexpected results because my webstorm testacular server was running on 9877 instead, but I had configured webstorm debug to run on 9876.
All good now.
I have written some software that makes use of the -app command line option in Firefox to launch XUL applications in Firefox's embedded copy of XULRunner. This all worked fine in Firefox 3.x, however when I try with Firefox 4, Firefox either crashes or does nothing (depending on if it is on Mac or Windows).
I have tried a number of other command line options and many of them seem to be variously broken. (such as -v to print the version information, which crashes on OSX)
Does anyone know if there are already registered bugs about this? Was the removal of -app intentional or was it an oversight? Is there any way to work around this problem?
The -app is maintained in firefox 4 and should work.
I do not know if there is a bug for windows and mac os, but I'm using it on linux for several apps, and it works well (my firefox version is Mozilla Firefox 4.0.1)
Just wanted to bump this - as on Firefox 7, -app does not seem to be there:
$ uname -s -r
Linux 2.6.38-11-generic
$ firefox --version
Mozilla Firefox 7.0.1
$ firefox --help
Usage: firefox [ options ... ] [URL]
where options include:
X11 options
--display=DISPLAY X display to use
--sync Make X calls synchronous
--g-fatal-warnings Make all warnings fatal
Firefox options
-h or -help Print this message.
-v or -version Print Firefox version.
-P <profile> Start with <profile>.
-migration Start with migration wizard.
-ProfileManager Start with ProfileManager.
-no-remote Open new instance, not a new window in running instance.
-UILocale <locale> Start with <locale> resources as UI Locale.
-safe-mode Disables extensions and themes for this session.
-jsconsole Open the Error console.
-browser Open a browser window.
-new-window <url> Open <url> in a new window.
-new-tab <url> Open <url> in a new tab.
-preferences Open Preferences dialog.
-search <term> Search <term> with your default search engine.
-private Enable private browsing mode.
-private-toggle Toggle private browsing mode.
-setDefaultBrowser Set this app as the default browser.
-g or --debug Start within debugger
-d or --debugger Specify debugger to start with (eg, gdb or valgrind)
-a or --debugger-args Specify arguments for debugger
I too would love to know when and why it was removed, but I simply cannot find any info online (see also Single-file app with xulrunner - possible?) ...
PS: Just filed a bug here: Bug #880596 in firefox (Ubuntu): “Option '-app' missing from Firefox above version 3” - I thought it would be automatically copied to mozilla's bugzilla (seeing bugs like Bug #207454), but unfortunately, it wasn't so... - bugzilla bug needs to be copied and added manually, it's there now...
I also experienced problems using the -app switch. I'm using Firefox 10, but I have an idea this problem goes right back to FF 4.
The firefox binary, when run with the -help option, does not show list the -app option, which caused me much confusion, but I believe its still there.
The problem for me, instead, was to do with this change in Firefox 4, requiring a chrome manifest file in the application root. Since FF 4, only a single (root) chrome manifest is read, so you must create one with the following line, (or lines, if you want to have multiple manifests).
manifest chrome/chrome.manifest
Then launch the application the usual way
firefox -app path/to/application.ini -jsconsole
(For debugging use the -jsconsole option).
Another note, (you didn't mention having tried this, but I did and it was wrong) -- don't use the -no-remote option. I tried this with the intent of starting a new process for my XUL application separate from already running firefox instances. However, the -app option will create a new process for your application even if firefox instances are already running, so there is no need.
See also this question for more info about the chrome manifest issue.