I want to start using Microsoft Playwright for my web application. When running npx folio to start my tests its targeting this folder by default C:\Users\john\AppData\Local\ms-playwright\firefox-1225\firefox\firefox.exe but that is not where I want it to target.
It results in an error when running npx folio because firefox.exe does not exist in that directory
C:\Users\john\AppData\Local\ms-playwright\firefox-1225\firefox\firefox.exe does not exist...
How do I get pass this?
Related
I have installed Hyperon a business rule engine on windows machine.
I have fallowed instruction to install it from:
- https://www.hyperon.io/tutorial/installing-hyperon-studio
After installation I have browse below URL to see whether #Hyperon web app is running or not.
http://localhost:38080/hyperon/app
I am getting this error:
Error Screenshot
Reproduceable Steps:
Downloaded hyperon zip and extracted it.
Open the file directory and reach to the /bin folder
Opened it in command prompt:
Ran startup.bat file.
Refer to below screenshot:
command prompt logs
tomcat command prompt logs and output after executing- startup.bat
Such effect occurs when trying to run hyperon with JDK 8.
Hyperon Studio requires JDK 11.
See installation guide:
https://www.hyperon.io/tutorial/installing-hyperon-studio
If you have multiple JDKs installed, you can swith to proper by setting JAVA_HOME variable:
for example:
cd c:\hyperon-studio-2.1.9\bin
set JAVA_HOME=c:\java\jdk-11.0.4
startup.bat
The first run may take a minute, because hyperon needs to initialize database schema.
Once it is fully started you will see hyperon.log file and should be able to access localhost:38080/hyperon/app.
I am having issues with cy.visit hanging in electron only, but chrome is fine. There are no errors in the console with cypress run, so would like to run cypress open with electron, but not sure how. cypress open --browser electron or node_modules/cypress/bin/cypress open --browser node_modules/electron/dist/Electron.app/Contents/MacOS/Electron doesn't work.
I have tried cypress run --headed but cypress run doesn't allow you to stop the test mid way through and investigate what is wrong. Pausing the test closes the window.
As stated in the docs about the open command, the browser flag is used only to specify a path to a custom browser to be added to the list of available browsers in Cypress. Electron being the default browser bundled with Cypress, you don't have to specify it when launching the UI. You can choose any browser you need on the UI before launching a test suite (see screenshoot).
I have some Robot Framework tests for Android device which I'm running. I'm currently using Windows10 computer to develop those tests.
I just installed version v1.15.0-1 of Appium. By default this new Appium is using UIAutomator2. Not anymore UIAutomator1. My problem is, that I have installed UIAutomator2, but Appium not seem to find that. Only way I can run my tests is to use UIAutomator1.
I have installed UIAutomator2 driver:
npm -g install appium-uiautomator2-driver
Not working:
Open Application ${REMOTE_URL} platformName=${PLATFORM_NAME} platformVersion=${PLATFORM_VERSION} deviceName=${DEVICE_NAME} appPackage=${${ENV}_APP_PACKAGE} automationName=UiAutomator2 app=${${ENV}_APP} appActivity=com.dummyfi.viestit.ui.splash.SplashActivity noReset=True
Working:
Open Application ${REMOTE_URL} platformName=${PLATFORM_NAME} platformVersion=${PLATFORM_VERSION} deviceName=${DEVICE_NAME} appPackage=${${ENV}_APP_PACKAGE} automationName=UiAutomator1 app=${${ENV}_APP} appActivity=com.dummyfi.viestit.ui.splash.SplashActivity noReset=True
This is what I get, when I'm trying to run tests with UIAutomator2:
Suite setup failed:
WebDriverException: Message: An unknown server-side error occurred while processing the command. Original error: The application at 'fi.dummy.viestit.sa' does not exist or is not accessible
With UIAutomator1, everything is working fine.
I get an error as below when I try to run my tests on device farm.
testAppiumMethod failed: Invalid server instance exception has occured:
There is no installed nodes! Please install node via NPM
(https://www.npmjs.com/package/appium#using-node-js) or download and
install Appium app (http://appium.io/downloads.html)
I have installed Appium globally on local machine and the tests run fine. But they fail on device farm(have included all the dependencies). Can somebody help me out?
I believe you are trying to invoke the Appium server through your code, which is not required in Device Farm. Device farm has a Test Spec file (which is a yaml file) which does it for you, so all yo need to do is connect your driver to the invoked Appium server.
When you get the chance would you be able to provide this info:
appium verion being used
Specific method that the this failed on/code
snippet
Programming language Java/python
How exactly are the test being packaged and uploaded? Are we using the web console or the SDK/CLI?
Is this a web app tests or native app tests?
Also, to rule out an issue with a specific device would we be able to run the AWS Sample app/test on the same device?
Assuming this is an android test execute these commands to build the sample app:
git clone https://github.com/awslabs/aws-device-farm-sample-app-for-android.git
cd aws-device-farm-sample-app-for-android/
./gradlew cC
The app-debug.apk should be located in ./app/build/outputs/apk/
Then clone the sample appium testng tests:
git clone https://github.com/awslabs/aws-device-farm-appium-tests-for-sample-app.git
cd aws-device-farm-appium-tests-for-sample-app/
mvn clean package -DskipTests=true
The test pacakge "zip-with-dependencies.zip" should be located in the ./target directory
My apologies for adding all these questions as an answer. I look forward to your response.
HTH James
Seems to me that you need to install node on your AWS instance.
See below:
https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/setting-up-node-on-ec2-instance.html
Im trying to translate my chrome app to ios. I run the command cca create myapp --copy-from=manifest.json Some errors exist cp: copyFileSync: could not write to dest file (code=ENAMETOOLONG): $PATH_TO_PROJECT/project/platforms/ios/www/platform/..../www/platform/config.xml
where .... is 40 repeated directories of /www/platform
The translation succeeds and im able to run my project with android however, when trying to run in xcode i see an almost identical error saying File name too long.
Anyone have simmilar issues? Anyone able to get ios translations to run?
This is the result of a bug in the way we "import" your project when you specify --copy-from or --link-to arguments to cca create when your import directory is the same as your output directory.
Since the import in your example is a parent folder of the output, it copies itself over and over, recursively until the system kills the process. We have added protection against doing this (by warning during cca create if we detect this case), but that version hasn't released to npm just yet (sorry!).
The fix for the issue is simple: just create your project in another directory that is outside of your packaged app! i.e., either:
# From within packaged app directory
cca create ../myapp --copy-from=./manifest.json
or
# From outside packaged app directory
cca create myapp --copy-from=$APP_DIR/manifest.json