Likelihood to Recommend
1. It's open source which supports range of languages, operating systems and languages. Well suited for Android and IOS mobile automation. Supports all kinds of apps, which makes it flexible and robust mobile testing tool 2. It is less appropriate where we need intercept network call to verify the API calls. Extensive coding experience is required to work Appium
Read full review
Domino is best in medium-sized businesses of 20-100 employees. It's too complicated to implement in very small companies unless you have good external resources. It scales up very well for larger companies but the pressures of users wanting particular "brand-name" software can become difficult. If you want a restricted "extranet/portal" system for a limited set of members it's a great system, particularly if you add a Domino CRM on top. Unlike Microsoft, you never have to resort to command-line tools, like PowerShell, in Domino to get things done.
Read full review Pros It uses WebDriver API so it makes it easy to use for former web test automation engineers. It can be managed via the command line via an extensive set of parameters. It handles implicit waits at the server side that is especially valuable in distributed infrastructure. Read full review Domino support for policy-based user registration and deployment eases end-user creation. User access to databases is simplified via group membership and defined roles. Email replication to clustered servers is simplified through connection/replication documents stored centralized address book Group calendaring enabled at client level controls. Read full review Cons Element browser sometimes is unreliable and has sporadic fails. Appium running is a bit slow, compared to tests written with Appium and with Espresso or XCTest. Read full review User interface needs to be modernised. Read full review Alternatives Considered
If you're an Apple developer, you use Xcode. It's practically a forced necessity. For system testing though, it doesn't have to be. You can have your development team focus on unit and integration tests in their platform and another team automate acceptance tests with a language they are more familiar with.
Read full review
, SQL and Teams but only for the things that they excel in. For example, we use teams for small team interactions (including external participants). We use teams for meetings too. We've discovered that Teams collaboration is not as full-functional as Domino and more importantly, that our members (financial services) do not trust the Open Office365 cloud.
and Team collaborative features are often blocked in our member organizations. Domino is much easier to identify and unblock at the firewall level. It's much easier to restrict collaboration to approved options in Domino.
Read full review Return on Investment Appium is open source, so it's free. That's budget friendly right there. The ability to write mobile automation tests has saved considerable time for our manual test team, but that is true with most automation tests. We use Sauce Labs with our other automation, but Appium works great with Sauce Labs, as well, if I needed to run on emulators and simulators. Read full review The immediate impact on my organization as a non-profit is cost. Enterprise pricing for a Domino solution is exponentially more inexpensive than more popular applications. Of the most obvious impacts is user familiarity. Given a vast majority of the employment pool having familiarity with MS products, orienting new employees to Domino\Notes is burdensome. Adoption is slow and resistance is high. Hiring Domino administrators and developers is increasingly challenging. The recent sale of the Domino platform away from IBM is concerning. Read full review ScreenShots