AWS Device Farm vs. Kobiton

As long as you have the right scenarios in mind where you can use AWS Device Farm, you will be very happy. It's a cloud platform for testing automation support, where you can use real devices in multiple configs to validate your Android or iOS use cases. It does easily integrate with your CI pipeline, but reporting and UI are not perfect. A pain point is also the JUnit4 implementation, which could be more mature.

Incentivized

When it comes to doing or performing testing on the applications or devices then Kobiton is the best option to go forward with. Kobiton is best for both manual and automation testing. It also comes with great features like appium scripts generation which really useful and less time-consuming and makes it really good to go with.

Incentivized

• Easy testing on many different devices
• Great integration with development workflow
• Customizable selection of testing framework

Incentivized

• Interface (CLI) not very easy. Competition has better options.
• Integration with IDE for test case coding.
• Reporting for the test scripts executed.

Incentivized

We had the enterprise support with AWS, so overall support experience was good with great engineers on the back providing answers. As you may know, overall AWS support is different and this is not different. Responses through the regular web support channel came easily, fast and accurate. We had questions/issues which were solved fast. Documentation is good as well, especially around the test automation pieces.

Incentivized

We haven't used anything like AWS Device Farm before. I am familiar with Amazon Web Services and when we had our MVP ready to test, we turned to AWS for a solution. AWS Device Farm was exactly what we were looking for as we have a really small team and limit resources.

Incentivized

• It impact more and more. Not in terms of ROI but in time as well

Incentivized