Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Groovy for Domain-Specific Languages, Second Edition

You're reading from   Groovy for Domain-Specific Languages, Second Edition Extend and enhance your Java applications with domain-specific scripting in Groovy

Arrow left icon
Product type Paperback
Published in Sep 2015
Publisher
ISBN-13 9781849695404
Length 386 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Fergal Dearle Fergal Dearle
Author Profile Icon Fergal Dearle
Fergal Dearle
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Introduction to DSLs and Groovy FREE CHAPTER 2. Groovy Quick Start 3. Essential Groovy DSLs 4. The Groovy Language 5. Groovy Closures 6. Example DSL – GeeTwitter 7. Power Groovy DSL Features 8. AST Transformations 9. Existing Groovy DSLs 10. Building a Builder 11. Implementing a Rules DSL 12. Integrating It All Index

Spock as a DSL


Test-driven development (TDD) has become an essential capability for software developers over the past decade. TDD can mean different things to different organizations. It can mean the adoption of a full-blown test first style of coding, where unit tests are written before any functional code. It could just mean that you write extensive unit tests for every piece of functional code in the system. It may or may not mean the use of continuous integration builds that run a battery of unit tests after each code check in. Whatever TDD means to your organization, the chances are that flavors of xUnit test frameworks, including JUnit, WEBUnit, and HTTPUnit have been essential tools in your software developer's arsenal for some considerable time now.

The problem with xUnit-style testing is that these are all tools that are designed by programmers, for programmers. Your QA staff might be familiar with running xUnit tests and reporting on problems that they encounter, but they are less...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime