Developers, Don’t Write Functional Tests! - A Practitioner's Guide to Successful Software Testing, Part 1 « mgm technology blog. Over the past few years I have noticed that the distinction between functional tests and unit tests has blurred in a lot of projects.
I think that using the features of modern testing frameworks like JUnit and TestNG to push functional tests into unit tests is the wrong approach, because it shifts the focus of the test from the test perspective to the development perspective. In this blog post, I explain in detail how I have come to this conclusion. In order to facilitate the discussion I want to elaborate the arguments using a simplified example, the development of an online shop.
Let’s call the artefact of the development effort a product. New Open Source Project: Selenate. The future of functional web testing? The Groovy community is a productive bunch, which means there are a plethora of frameworks, libraries, and tools to make your life easier.
The area of testing seems to be particularly fertile ground and I've recently been looking into a couple of tools that, when combined, promise a step change in your productivity when writing functional web tests. Although my usual focus is Grails, you don't have to use Grails to reap the benefits of these tools: they will work with any web application and will integrate well with any Java-based project/build. As it happens they both have associated plugins that make using them from Grails pretty straightforward. The first of the tools I want to talk about is Spock.
Tellurium.