My cypress version updated to:
Cypress package version: 10.3.0
Cypress binary version: 10.3.0
Electron version: 18.3.0
Bundled Node version: 16.13.2
And ever since then I have an issue where a webpage that used to load after a test runs a login and then presses login, the webpage (on a subdomain, a checkout page) now doesn't load, the website shows itself to be loading but it's almost as if something is stopping in, some content appears but not all of it.
Is there a setting or anything I need to change?
Only seems to happened since V10, I could downgrade but i'd rather get it working in the latest version.
Related
Hello I tried to upload react native iOS app to App Store. the upload is succefull but when I try to see the build in testFlight it show like this
as you see it show me the version but inside it is empty. then after one minute even the version number disappear and it asks me to upload again. I uploaded it many time but still the same thing
The version disappears if there is another upload with the same version number. Change the version and try to upload the app again.
sorry for the late answer. the issue was the firebase npm packages were not the latest version and it was causing an issue during uploading. So remove all firebase npm packages and install them again after that upload the app.
I'm trying to automate the task of downloading mp3 files from a web site and uploading to another web site. With Puppeteer, I'm able to do this with the following code.
// ... Download the file and save locally
// Sets the value of the file input to fileToUpload
inputUploadHandle.uploadFile(fileToUpload);
// ... submit the form
This works fine on my Mac. I can download the file and upload it through the form submit. When I deployed it on Heroku, I'm aware that Heroku's ephemeral file system will save the file to /app folder. And I'm even able to send that saved file through NodeMailer as an attachment.
But on my Heroku app, when Puppeteer submit the form, the file is not uploaded as it should be. The submit happens as if the file is not selected.
I know I can have work arounds like grabbing the file from my own server. But I'm still curious why this happens. What makes Puppeteer uploadFile to fail on Heroku?
By the way, here are two links that might help with the background:
Practical Puppeteer: How to upload a file programmatically
puppeteer-heroku-buildpack
The solution: if you want to use uploadFile, don't use Puppeteer version 2.1.1, for now stick to 2.0.0. In your package.json:
"puppeteer": "2.0.0"
I checked recently and found out that uploadFile is still broken in Puppeteer 5.5.0.
Here's the detail. When I develop on my Mac, I didn't specify a version for puppeteer. But I happened to be using a version in which uploadFile works. However, every time you push to Heroku, Heroku will check your package.json to install all dependencies. In my case, Heroku updated to the latest version (by the time of this writing 2.1.1) which broke the uploadFile function.
Even though I printed out the Chromium version early on and noticed that Heroku is using a higher version, it never occurred to me that I should test with an older version of Puppeteer. Instead, I spent a lot of time testing other workarounds, which all failed. Any way, once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth.
I'll post an issue on Puppeteer and hope this to be fixed in the next release.
I see WATIR supports Edge browser automation in official website. But when I tried to run my existing suite on Edge after setting the path for MicrosoftWebDriver.exe in environment variables I am facing the below error .
Selenium::WebDriver::Error::WebDriverError: unable to connect to
MicrosoftWebDriver localhost:17556
Below are my version details.
Watir - 6.8.4
Ruby - 2.2.6
Windows 10 64 bit
I even tried using webdrivers gem of titusfortner. But, no success webdrivers gem is not downloading MicrosoftWebDriver.exe into .webdrivers folder in my users directory.
I wanted to know whether I have anything wrong in my set up to trigger edge browser. Thanks in advance
Got the issue resolved. We have to download the right version of Microsoft WebDriver.
Go to Start > Settings > System > About and locate the number next to OS Build on the screen. This is your build number. Having the correct version of WebDriver for your build ensures it runs correctly.
Get the right version of driver at WebDriver - Microsoft Edge Development
I seem to be unable to find an answer to the question, does the godoc server support live reload changes in for my own projects?
According to this article it should be supported however whenever I change my code (update documentation) no changes appear until restart of the web server
My documentation updates/appear every time I start the the sever:
godoc -http=:6060 &
I don't want to restart the server for every change, is this expected behavior, what can I do to update my changes with the least amount of effort?
My go version:
$ go version
go version go1.8 darwin/amd64
Using browser with incognito mode:
Chrome Version 57.0.2987.133 (64-bit)
Godoc for a directory ("Directory /src/github.com/someuser" at the top) does not automatically update.
Godoc for a package ("Package yourthing" at the top) will automatically update, but you must reload the page to see the change.
So I've been having an issue getting my Protractor/Jasmine tests running in FireFox. I've been aware of the version issue from FireFox that doesn't support selenium angular/bootstrap etc etc and that has been my issue to date.
I was informed to try geckodriver but really can't find any good resources on how to set it up using protractor and jasmine. Or even which driver is the appropriate one to use.
Recently I've tried the following to get FF back up and running (all resulted with no luck):
Downgraded FireFox to as low as 33.x.x while keeping
Protractor/Jasmine at current versions (4.0.5 and 2.51 respectively).
Downgraded Protractor to as low as 3.0.0 while keeping FF at current version (47.0.1)
Downgraded both Protractor and FF to the lowest above versions.
Used Latest Version of FF 47.0.1 with lesser versions of Protractor.
Used Latest Version of FF 47.0.1 with latest version of Protractor 4.0.5
Used directConnect: true and directConnet: false
So I guess now I have one of two questions:
1. Could somebody post a protractor config snippet using the geckodriver / or direct me to a walk-through of this.
2. Inform me of a work around or a working solution (versions of both webdrivers/protractor/jasmine, etc).
If you need to see errors or my config file or anything at all please just simply comment and I'll be happy to revise.
There was a period of time around Firefox v46 and Selenium v2.5x where things were incompatible due to changes to the firefox web-driver. The issues were quickly addressed by the community.
The issue with Protractor lies with the webdriver-manager being a bit out of date with the updates. As per discussions on github, they are aware of this, and a fix is coming.
The workaround in the meantime is to manually update the outdated pieces.
Here's how you'd do it, run
webdriver-manager update
This will give you the paths to all the components the webdriver-manager handles for you.
Navigate to the selenium-server-standalone.jar file (protractor/node_modules/webdriver-manager/selenium/selenium-server-standalone-2.53.1.jar in my case) and replace this with the latest selenium standalone jar (anything v3+ should be good). Make sure to retain the exact filename as the previous jar file. (link: http://www.seleniumhq.org/download/)
Repeat the process to get the latest Gecko web-driver. Uncompress and replace the current version. (link: https://github.com/mozilla/geckodriver/releases)
Now run your tests through protractor and you should be good with the latest version of Firefox.
Good luck and happy testing :)