This presentation shows how to easily go from user stories to automated integration tests that themselves read like user stories. You can accomplish this by using custom domain-specific languages (DSL).
Too often our automated integration tests rely on coding and intimate technical knowledge of our systems, which not only limits who can write integration tests but also clouds our understanding of what the tests are actually doing. How can we assess our integration test coverage if we need to weed through densely written Java code? Don’t we run the same risk of errors in such test code that we encounter in our application code? It’s past time to fix this.