UNIT TESTING ANDROID STUDIO TUTORIAL CODE
The practice is to turns feature specifications (or user stories) into a set of unit tests and then writing code that satisfies those specs via passing tests. Behavior Driven Development has been around for decades.
Laying the foundations of your project with extensive testing is not a new idea. "If you can not measure it, you can not improve it." - Lord Kelvin Testing As You Go Testing your code for bugs and architectural flaws from the beginning solidifies your product to be manageable in the longer run. Obviously this is not a desirable situation. I have seen organizations rewriting already published products only because the code base has become unmaintainable due to spaghetti code that is rotten with bugs.
More often than not, the end result is that project becomes unmaintainable within a year. Obviously, when you are in a rush to take the product out as soon as possible, testing becomes least desirable practice. Not only the process is quite boring, it also requires a lot of repetitive boilerplate code to be written for even the most simplest scenarios, making testing a very time consuming process. This is often due to the complex and dull nature of old school JUnit based testing. Not just the crappy ones, but sometimes products with thousands of users. More than half of the code bases you will come across will have little to no tests. Since I mostly work with Android applications. In this post, let's understand why unit tests serve as the backbone of successful products and learn a new way of writing tests that is much simpler, intuitive and appealing. While almost every developer understands the value of testing their code, most of us fall prey of laziness in the face of approaching deadlines and prospect of more exciting work. Testing is hard and not everyone likes to spend their time writing unit tests when they could be building shiny new features.
0 kommentar(er)
