CRO
Test-Driven Development (TDD) for Android
## Cassandra Shum
## Estimated time to complete: 2h 35m
## Topics Native Android Development
## Published byAddison-Wesley Professional 2016
>> 2018x11
>> 47x350
// http://www.pearsonitcertification.com/
\\ https://www.safaribooksonline.com/
// https://www.informit.com/
Continuous Delivery (CD) is an agile practice that's had
a big impact on how many people think about developing
software. It forced us to start thinking that software
is only "done" when it is released. With more features
reaching the done stage sooner, CD practices have
enabled us to get early feedback from users and taught
us a lot about testing, monitoring, and automating our
delivery along the way. But mobile development has often
been left behind. Or has it?
Testing is an important component of CD and shouldn't be
taken for granted or ignored, especially when developing
mobile applications. The process of setting up a
testable environment and writing tests, however, can be
a challenge. Implementing unit tests and following
principles of test-driven development for mobile apps--
whether native or hybrid--is often counterintuitive. To
guarantee that each component in your mobile app works
properly for the set of inputs you expect, it is
important to test each component (or unit) of an
architecture independently and to simulate different
system states based on the supplied input to the test,
while covering exotic cases in the process.
Description
In Test-Driven Development (TDD) for Android,
ThoughtWorks Lead Consultant Cassie Shum takes a deep
dive into the critical role of TDD in mobile
development. This video quickly reviews Continuous
Delivery best practices and the role of CD in mobile
development. The video then focuses on the role of TDD,
showcasing how to use tools for unit testing and UI
testing by demonstrating with Android testing frameworks
Robolectric and Espresso.
WEE ASUMME NO LIIABILLITY FUR A WROONG SPELING
COZ WEE ARRE A NON (iL)LiTERATE GRUP!!
TANNKS TU THE LITERATE ASKII FRIIEND!!