We’ve spent a lot of brainpower thinking about different design architectures and patterns. We are already building expertise with Gradle and will continue using these skills. We wanted to continue to rely on Robolectric as we moved to Android Studio, and as a consequence, the Gradle build system.Having our testing tool run seamlessly within our IDE allowed us very fast turnaround on a red/green/refactor workflow.Configuring Robolectric within IntelliJ + Maven allowed us to easily run tests from within the IDE, get immediate visual feedback, run subsets of tests and debug and set breakpoints within tests.In our consulting projects, we’ve benefited from building a solid set of unit tests with Robolectric, for a few reasons: Android Studio recently moved out of beta, so now is a good time to share about our successes so far. However, we still had trouble integrating some of the tools and techniques that made our past projects so successful. This shift has allowed us to build a uniform skillset, enhancing both our teaching and consulting. In May of 2014, we made the switch to Android Studio as our preferred Android IDE, migrating away from Eclipse in our Android bootcamps and book.Īs we have started new app development projects for clients, we transitioned away from IntelliJ, our previous IDE of choice. UPDATE: This post has been superseded by a newer version here.
0 Comments
Leave a Reply. |