Espresso vs. NetBeans

• It is very easy to verify Images with drawable resources
• Color Verification we can do this by referring to the same hex code as the developer team used so that it is reused.
• Opening a desired activity without performing End-to-end flow which eventually saves time.
• If the application is built on Android we can go testing activity with Espresso as it provides all the necessary APIs
• Espresso is not appropriate to iOS app automation, from a business point of view we need to hire new resources for iOS testing.

Incentivized

If your organization works with developing or supporting Java applications and is focused on running efficiently with a lean budget, NetBeans would be a good choice to consider.

If your development staff uses other languages, or prefers a high level of available professional IDE support, it may be better to consider a paid option if your budget allows.

• Automatic Waiting logic before failing any test
• Black box and Grey box testing
• Easy to Understand and Very Flexible
• Supported Java And Kotlin
• Fewer Efforts compare to other Mobile Automation Frameworks
• Execution is very Fast

Incentivized

• Great code completion, just start typing some code and the program will fill in the code.
• Find/Replace is a key feature and works through whole projects as opposed to just a single file.
• Side by side code comparison right in the interface allows me to update similar pages.
• I appreciate the ease of using variable highlighting, with a wave of the mouse you can see visually where a given variable exists in your code.

Incentivized

• 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

Incentivized

• Heavy software needs more RAM. It does tend to use a lot of your computer's resources if you're loading up a huge project and slow things down.
• Problems with configuring plugins.
• With every release of a new version, there are some bugs which create problems while coding.

Incentivized

Netbeans enhances my coding work, shows me where I have errors and helps find variable instances. I would be lost without find/replace in projects functionality as I use projects as templates for new projects. Occasionally the code hints aggravate me, but I understand that it is actually making me a better coder, working to get the 'green light' of a clean file with no errors or clumsy code.

Incentivized

NetBeans has a very strong user community. We can find solutions here for almost all the problems we face. In addition, we can forward NetBeans Support teams the problems we cannot solve. We can get quick feedback from the support teams, but I generally try to solve my problems by following the forums.

Incentivized

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.

Incentivized

IBM Rational Application Developer and IntelliJ IDEA are great with hell lot of features packed into the product and are subscription based. However, most of the features they were providing were moot from my organization's business perspective and the cost was expensive. Eclipse is an opensource product with great features, but is difficult to configure and use as compared to NetBeans. One of the frustrating issues we faced with Eclipse was its slowness while saving a file. http://https//stackoverflow.com/questions/40166270/eclipse-neon-pathetically-slow

Incentivized

• As it is an Open Source tool it cost-effective
• East to use, so that you can train many new Joiners to start delivering the tasks
• Maintainance is very low, as we depend on the developer's layout files we can reuse their elements
• We can cover most of the scenarios which helps in the coverage of the tests

Incentivized

• It changed my way of coding. In my early days of development I never indented code, but with NetBeans my coding way has changed.
• One IDE for all languages. I can write code in PHP, HTML, CSS, and JavaScript in only one editor or IDE.

Incentivized