Java IoT Authors: Liz McMillan, Elizabeth White, Yeshim Deniz, Zakia Bouachraoui, Pat Romanski

Related Topics: Java IoT

Java IoT: Article

Catching the Test Bug

If you don't already use JUnit, you should

The software industry is often obsessed with progress be it in the form of a new language, wire protocol, specification update, or some other technology-driven feature. For me, software is a means to an end, and progress should be measured in features that allow code to be written more efficiently, with fewer errors, and with an increased fitness of purpose. To this end, the single thing that has most changed the way I view and approach Java is the JUnit framework.

I first came across JUnit working on a project where I was designing an API specification for a developer eight time zones away. Rather than having documents flying back and forth, he convinced me that I should write JUnit tests for the API. None of them worked. In fact to begin with none of them even compiled cleanly because the code didn't exist; however, the concept worked perfectly. The contract between the specification for what the code would do and all the assertions for how it should behave were all defined in a single place that was alive and coupled to the code. Whenever anyone new came along and wanted to know how the class library was supposed to work, we just said "check out the JUnits." No need to have spec-ware documents that would get out of step and become inevitably dated. With the unit tests representing the specification for how the code should work as part of the same code repository as the program source, the two could be refactored together, and in a short time I became totally hooked.

On a subsequent project we created a rule - before any developer checked code into the repository, he had to run all of the JUnit tests in the workspace. Initially people squealed and complained about lack of productivity and so forth; however, it proved to be a cornerstone of the project's eventual success. I remember one bleak day when some code I'd changed had, unbeknownst to me, broken another part of the system. The developer of the piece I'd broken was furious, not at me (although he was a little peeved), but more at himself for not having written a unit test that would have shown the breakage. His view is that unit tests are an insurance policy that a piece of code you write does what it says it is going to (using assert statements and other JUnit test constructs), but more important that by making your test part of the larger test suite, each time a developer makes a change, she can see the breakage and either fix the code, or fix the test if it's no longer applicable. Another thing we adopted on the project is that whenever a defect was raised, the first task was to write a failing test. This could take the better part of a day, sometimes longer, even if the fix was only a 10-minute hack. The benefit however is that once the failing test goes from red to green and both code and test alike are committed to the repository, there should be no way the problem can re-occur. The more tests we had in our suite, the better our insurance coverage.

For any project I work on now the tests form part of the build process. It's not enough to have a clean compile; you have to have a clean run of all of the tests for a build to be blessed as "complete" from development and taken to the next stage of the production process. This makes the functional testers happy as what they're getting is higher quality, allowing them to spend more time looking for integration or usability problems. It also lowers the entry bar for new developers as the project now has an insurance policy against sloppy regression in the form of an integral suite of unit tests.

I now view JUnit as an integral part of the Java development process, as important as compilation; one picks up syntactic compilation errors and the other safeguards runtime behavior. If you don't already use JUnit, you should, and then you too can catch the test bug.

More Stories By Joe Winchester

Joe Winchester, Editor-in-Chief of Java Developer's Journal, was formerly JDJ's longtime Desktop Technologies Editor and is a software developer working on development tools for IBM in Hursley, UK.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

IoT & Smart Cities Stories
The deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-c...
Machine learning has taken residence at our cities' cores and now we can finally have "smart cities." Cities are a collection of buildings made to provide the structure and safety necessary for people to function, create and survive. Buildings are a pool of ever-changing performance data from large automated systems such as heating and cooling to the people that live and work within them. Through machine learning, buildings can optimize performance, reduce costs, and improve occupant comfort by ...
The explosion of new web/cloud/IoT-based applications and the data they generate are transforming our world right before our eyes. In this rush to adopt these new technologies, organizations are often ignoring fundamental questions concerning who owns the data and failing to ask for permission to conduct invasive surveillance of their customers. Organizations that are not transparent about how their systems gather data telemetry without offering shared data ownership risk product rejection, regu...
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Poor data quality and analytics drive down business value. In fact, Gartner estimated that the average financial impact of poor data quality on organizations is $9.7 million per year. But bad data is much more than a cost center. By eroding trust in information, analytics and the business decisions based on these, it is a serious impediment to digital transformation.
Digital Transformation: Preparing Cloud & IoT Security for the Age of Artificial Intelligence. As automation and artificial intelligence (AI) power solution development and delivery, many businesses need to build backend cloud capabilities. Well-poised organizations, marketing smart devices with AI and BlockChain capabilities prepare to refine compliance and regulatory capabilities in 2018. Volumes of health, financial, technical and privacy data, along with tightening compliance requirements by...
Predicting the future has never been more challenging - not because of the lack of data but because of the flood of ungoverned and risk laden information. Microsoft states that 2.5 exabytes of data are created every day. Expectations and reliance on data are being pushed to the limits, as demands around hybrid options continue to grow.
Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities - ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups.
As IoT continues to increase momentum, so does the associated risk. Secure Device Lifecycle Management (DLM) is ranked as one of the most important technology areas of IoT. Driving this trend is the realization that secure support for IoT devices provides companies the ability to deliver high-quality, reliable, secure offerings faster, create new revenue streams, and reduce support costs, all while building a competitive advantage in their markets. In this session, we will use customer use cases...