Summary of A World of Possibilities with Java ME + Bluetooth + Arduino
This presentation advocates for creating automated integration tests that mimic user stories using custom domain-specific languages. It argues that traditional coding-heavy tests obscure their purpose and limit accessibility. By adopting these specialized languages, teams can improve test coverage assessment and reduce errors inherent in complex technical code, making tests more understandable for everyone involved.
Parts used in the Automated Integration Tests Project:
- User stories
- Automated integration tests
- Custom domain-specific languages
- Java code (traditional method)
“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.
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.”
Copyright © 2013 Oracle and/or its affiliates. Oracle® is a registered trademark of Oracle and/or its affiliates. All rights reserved. Oracle disclaims any warranties or representations as to the accuracy or completeness of this recording, demonstration, and/or written materials (the “Materials”). The Materials are provided “as is” without any warranty of any kind, either express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, and non-infringement.
- How can we make automated integration tests read like user stories?
You can accomplish this by using custom domain-specific languages. - What limits who can write integration tests in traditional approaches?
Reliance on coding and intimate technical knowledge of systems limits who can write them. - Does traditional test code cloud our understanding of what the tests are doing?
Yes, relying on densely written Java code clouds the understanding of what the tests actually do. - How can we assess integration test coverage if we use traditional methods?
It is difficult because you need to weed through densely written Java code. - Do we run the same risk of errors in test code as in application code?
Yes, there is a risk of encountering the same errors in such test code as in application code. - Why is it past time to fix the current state of integration testing?
Because current methods rely too heavily on coding which limits accessibility and clarity.
