Need advice about which tool to choose?Ask the StackShare community!
I am looking to purchase one of these tools for Mobile testing for my team. It should support Native, hybrid, and responsive app testing. It should also feature debugging, parallel execution, automation testing/easy integration with automation testing tools like Selenium, and the capability to provide availability of devices specifically for us to use at any time with good speed of performing all these activities.
I have already used Perfecto mobile, and Sauce Labs in my other projects before. I want to know how different or better is AWS Device farm in usage and how advantageous it would be for us to use it over other mentioned tools

Stability - Just works. Availability - More than 15 datacenters. Enterprise features like SSO, local testing and SOC2/GDPR compliant.

BitBar's Dedicated Devices would be a great option for you. It allows you to dedicate (reserve) devices for your use only which also having access to all of the devices in the shared cloud. BitBar has the features and integrations that you are looking for as well.
In the company I will be building test automation framework and my new company develops apps mainly using AngularJS/TypeScript. I was planning to build Protractor-Jasmine framework but a friend of mine told me about Cypress and heard that its users are very satisfied with it. I am trying to understand the capabilities of Cypress and as the final goal to differentiate these two tools. Can anyone advice me on this in a nutshell pls...
I've used both Protractor and Cypress extensively. Cypress is the easier and more reliable tool, whereas Protractor is the more powerful tool. Your choice of tool should depend on your specific testing needs. Here are some advantages and disadvantages of each tool:
Cypress advantages:
Faster
More reliable (tends to throw fewer intermittent false failures)
Easier to read code (handles promises gracefully)
Cypress disadvantages:
Cannot switch between browser tabs
Cannot switch to iFrames
Cannot specify clicks or keypresses explicitly as if a real user was interacting
Cannot move the mouse to specific co-ordinates
Sometimes has trouble switching between different top-level domains, so not good for testing external links
Cypress is a newer tool with less extensive documentation and less community support
Protractor advantages:
More powerful because it is Selenium-based - it can switch between tabs, it can handle external links to other domains, it can handle iFrames, simulate keypresses and clicks, and move the mouse to specific co-ordinates within the browser.
More extensive community support and documentation
Protractor disadvantages:
Slower and more brittle - in general there is a higher likelihood of cryptic and/or intermittent errors which may cause your tests to fail even though there is nothing wrong with your application
For highly experienced automation engineers, the fundamental "brittle" nature of Selenium can be worked around - it can be reliable but only if you really know what you are doing
Less graceful handling of promises - relies on async/await or .then to manage the order of execution. Therefore it is a bit harder to read the code.
Harder to set up, and the method of setup impacts its reliability. For example, a hub/node configuration where the selenium jar is on a different physical machine than the browser under test will cause unreliability in your tests. Not everyone knows about this type of thing, so it's common to find Selenium frameworks that are set up poorly.
It's probably better to use Cypress if
you're at a smaller company and have a close relationship with developers who can help write hooks or stubs in their code to assist your testing
you don't need to do things like switch between tabs or test links to external top-level domains
It's probably better to use Protractor if
You might need to switch between tabs or test external links to other domains within the scope of your framework
You want to use a more accurate simulation of how a real user interacts with a browser (i.e. click at this location, type these keys)
You're at a company where you won't have any support from developers in writing hooks or stubs to make their code more testable in a less powerful framework like Cypress
Please try Handow, the e2e tool basing on Puppeteer.
Gherkin syntax compatible
Chrome/Chromium orentied, driven by Puppeteer engine
Complete JavaScript programming
Create test suites rapidly without coding (or a little bit), basing on built-in steps library
Schedule test with plans and arrange stories with sequential stages
Fast running, execute story groups in parallel by multi-workers
Built-in single page report render
Cover page view, REST API and cookies test
As we all know testing is an important part of any application. To assist with our testing we are going to use both Cypress and Jest. We feel these tools complement each other and will help us get good coverage of our code. We will use Cypress for our end to end testing as we've found it quite user friendly. Jest will be used for our unit tests because we've seen how many larger companies use it with great success.
Pros of Cypress
- Open source27
- Great documentation21
- Simple usage19
- Fast18
- Cross Browser testing10
- Easy us with CI9
- Npm install cypress only5
- Good for beginner automation engineers1
Pros of Sauce Labs
- Selenium-compatible60
- Webdriver compatible46
- Video recordings of every test35
- Qa31
- Mobile support29
- Any programming language26
- Developer tools23
- Test local and firewalled servers21
- Jenkins integration20
- Pristine VMs18
- CI Compatible17
- Appium support11
- Parallel testing9
- Rapid environment preparation8
- Easy testing on almost any device7
- Mobile device support7
- Allows me to Focus more test automation rather than IT7
- Secure testing and easy setup6
- Easy setup with CI and fast automated tests5
- Quick support response5
- Fast and reliable to host the automated tests4
- Easy to setup and understand,4
- Easy setup and integration with Travis Ci3
- Maintained browser matrix3
- Easy onboarding, do not need to manager VMs/OS/Browsers3
- Efficient tool to verify product quality2
- Teamcity Integration and mobile testing win2
- Hany for platform testing2
- Great documentation2
- Generous free trial2
- Easy. Straightforward. Scalable2
- Great way to integrate test suite on cloud2
- Simplicity of Sauce-connect2
- Very Good, Quick, flexible Infrastructure Support1
- It's great for my QA work1
- Awesome tech support1
- Having this available for CI servers is fantastic1
- Amazing service to do cloud cross browser testing1
- Depth of integrations1
- Because of its cloud based support for appium1
- Easy setup, Works great with selenium.1
- QE support1
- Manuals are not very well versed for beginners1
- Secure testing1
- Cheaper than browserstack1
- Stable1
- Simple to set up and integrate so many browser configs0
Sign up to add or upvote prosMake informed product decisions
Cons of Cypress
- Cypress is weak at cross-browser testing20
- Switch tabs : Cypress can'nt support13
- No iFrame support12
- No multiple domain support9
- No page object support9
- No file upload support8
- No support for multiple tab control8
- No xPath support8
- No support for Safari7
- Cypress doesn't support native app7
- Re-run failed tests retries not supported yet7
- No support for multiple browser control7
- Adobe4
- Using a non-standard automation protocol4
- Not freeware4
- $20/user/thread for reports4
- No 'WD wire protocol' support3
Cons of Sauce Labs
- Relatively slow2
- Expensive2