![]() ![]() You do not need this Action if the application to be tested is accessible over the public internet. This secure tunnel will be used by the remote browsers in BrowserStack to access your web application hosted in the GitHub Actions runner environment. Setup-local: This Action downloads and starts the appropriate BrowserStackLocal binary, thereby creating a secure tunnel connection from the GitHub Actions runner environment to the BrowserStack device cloud. The environment variables set up here shall be used by other BrowserStack actions as well for their functioning. Setup-env: This Action helps in setting up the required environment variables that are to be used in your test scripts. If you want to test your open source project on BrowserStack, then sign-up here for lifetime free access to all our products. You can sign-up for free trial if you do not have an existing account. You need a BrowserStack username and access-key to run your tests on the BrowserStack device cloud. The previous comparisons I have read online be appear quite old.This respository contains a library of GitHub Actions to help you integrate your test suite with the BrowserStack device cloud. Support for IE11 is also still required but no further back than that - thankfully! This browser also provides us with issues so using something like Browserstack OR Saucelabs OR …simply using our existing Selenium test suite, I felt would give us the capability to reuse what we already have on a realistic selection of devices until the confidence I mention was achieved …not only in our codebase implementation but also the test tooling.Ĭ is the on I have least knowledge of: Price wise it is considerably cheaper that the other two… but do you get what you pay for? However a combination of a) having to maintain multiple website codebases… some of them brand new and other very legacy b) high levels of evidence and governance required and c) real life experience of bugs found with our newer tech stack on mobile devices using iOS / Safari browsers (particularly) that have not manifested themselves using say Cypress on various viewports for example, mean that testing on real devices in the cloud is something that I see us doing …certainly in the short to medium term. I think it comes down to confidence in the tooling you suggest. Thanks for your reply Yogesh and I agree with much of what you are saying… in theory. There are free tools for visual regression and paid ones with some intelligent features like applitools.įor older browser versions, I have not worked on any app that ‘needs’ to support older, now insecure and off-support browsers (e.g. This testing is definitely important of your app is primarily used on mobile. This could either mean that our cross browser tests are rubbish or that we have not faced many incompatibilities even after such a long time (I’d let readers guess that )įor screen sizes and resolutions, there are several tools that allow you to change viewport and test app. In 1 year (several builds per day) of using cloud testing I have found 1 or two incompatibility issue with edge which I could have also found equally efficiently and probably faster using local cross browser testing using open source tools. It does depends on framework and libraries your app uses but because of standardization there are now less and less browser incompatibility issues compared to few years ago. Sorry, wasn’t much of help but I find the to tools very similar for what they offer.Īha, if it’s a web app, then given a chance I’d now think twice whether I really need to test on actual devices in cloud. testcafe itself provides us good cross browser testing capabilities and viewport testing (there are also other great tools like cypress, playwright, selenoid and zalenium. Ps: currently we used saucelabs with test Cafe (not selenium). we find it less beneficial to run it against different combinations of os, browsers, devices (considering today’s browsers have really good support for latest js, react and other libraries) since our app isn’t native but just a week based app that can be opened in browser.I personally liked saucelabs documentation better.both provide similar device support which is more than enough for most use cases.both were quite slow to execute tests compared to all maintained dockerized / local execution.both are easy to use and integrate in framework.I have compared browsers and saucelabs for web based app to be tested on different os, devices or browsers ![]() What are your requirements and is the app native, Web based or hybrid? ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |