In this chapter, we discovered Behavior-driven Development as an evolution of Test-driven Development, which we examined in previous chapters.

We discussed the driving forces behind Behavior-driven Development. We analyzed the concepts serving as the foundations, explored the Given-When-Then vocabulary idea, and introduced FitNesse and Slim as helpful tools in deploying tests.

We presented GivWenZen, a tool based on FitNesse that gives us the ability to create near-English, prose-style scenarios, and test them.

We introduced these techniques and tools to our sample Android project. However, we are still limited to test subjects that are testable under the JVM, avoiding the use of Android-specific classes and the user interface. We will be exploring some alternatives to overcome this limitation in Chapter 9, Alternative Testing Tactics.

The next chapter deals with a different aspect of testing, concentrating on performance and profiling, which is a natural step to follow after we have...