Espresso is a test framework used to write Android UI tests, and part of the Android SDK. The Espresso API encourages test authors to think in terms of what a user might do while interacting with the application - locating UI elements and interacting with them. At the same time, the framework prevents direct access to activities and views of the application because holding on to these objects and operating on them off the UI thread is a major source of test flakiness.
$0
ServiceNow Now Platform
Score 8.9 out of 10
N/A
The ServiceNow Now Platform is a digital workflow building and extension tool for ServiceNow featuring a number of low-code / no code tools.
ITSM is straight forward creation of Incidents and Requests. It can get more confusing as you layer more modules on top of it with event management, risk, project, etc. It also becomes more costly as everything is a different license. Integration between other external applications is very easy to do with their API. You can easily create endpoints for external apps to talk to or create REST messages for the platform to reach out directly.
As Espresso works on the ideal thread if the threads are not handled properly by the developing team it can lead to challenges in the execution of your tests.
Depends more on the developer's code
we cannot develop tests as individual frameworks, we share the repository with developers.
We need to be cautious while making changes in the tests, as we share same repository
The ServiceNow performance speed has big room for improvement, as it is quite slow in loading Dashboards with more than 5-6 widgets. We are keeping our ServiceNow version up to date with latest releases.
Usually there are issues with having multiple ServiceNow tabs open in the browser and have different dashboards open in those tabs.
The way of showing a history log of all activities on Incident ticket is not optimal and easy to use or search in and have very old design.
While we are very likely to renew, we are also assessing if we should renew all of what we currently subscribe to as we try to reduce costs. Some parts of the business feel there may be a better tool out there to fit their process requirements. We are currently working with them to identify what those requirements are to see if it makes sense while also pointing out a reduced cost of tooling is not always the best fit if we have an increased cost of customization and maintenance between tools.
It provides a lot of modification options which is wonderful for certain team usage but becomes too much of a job when it comes to the Service Desk. Also on the app support side, since too much information can be carried, it affects the GUI and makes it complex.
I was not in the team that take care of the installation of ServiceNow but their feedback was very positive. Go live was done by the planned date and their support at the beginning provided always a timely response. Their customer service is friendly and easy to reach. Today we don't use their customer service anymore because we have an internal IT dedicated to maintaining the system.
We went through a re-implementation last year with a partner and were very pleased with the outcome. We looked at several partners and chose one that was able to provide an entire scope and cost upfront of what would be required to complete our requirements. We worked very closely with the dedicated team assigned to our project throughout the process and they fully delivered on all of our requirements that we presented in the initial scope.
As our app is complete on Android Espresso is the best choice over Appium Fewer efforts in Espresso over Appium, as Espresso provides some built-in library to perform the operation. Easy to use, Espresso is very easy to understand and we can perform operations with very little code. Developers can contribute, as they have good command over Java and Kotin languages and also use Espresso for unit testing.
I've used Freshservice which is very similar to ServiceNow. I can definitely say ServiceNow performs better in a larger environment. Freshservice is usually used in smaller organization or less complx environment. Plus the ServiceNow reporting and dashboard features are more accurate than Freshservice. ServiceNow is a bit costly but gives way more features that really helps my organization.
1. It is not great when they can't seperate apps/products from a particular sku, forcing you to make a business case for a larger portion of functionlity than your current business case seeks to address. 2. ServiceNow reps are able to work with you when economies of scale are projected out. They are willing to start at a desired tier and provide pricing at applicable upgraded tiers
Very easy to use. Capture more data from the Incident and problem management. Easier to escalate and following the change management process to resole the issues.
Fast implementation of our Sales & Operation/Projects controls and process - tool adapted to our needs, not us to adapt to the tool.
Once we are a consulting/implementation company, our customers are happy to see that we use what we sell, and it is easy to show them how this platform/tool can have an impact on our own business.
