It’s quite common to build Spring Batch jobs in which the output is a file for distribution to another team, or to another business. These text files can be in various formats from delimited, fixed length, XML, or some other structure such as an MT950 formatted file (common in financial institutions). In a previous article, I discussed testing practices using …
Testing the Current Date/Time in Spring and Java
How often in Java services do we need to use the current date and time? Most of us would agree we use it quite often. Many times, we may want to record when an event happened, such as logging in, sending an invoice, or recording a chat. Other times, we may want to use the current time in a business …
Getting Started with Selenium Automation
Automated testing is a great way to ensure that any application can continue to grow and change while still giving fast and practical feedback to developers. This feedback can tell developers whether or not the changes introduced meet the requirements of the product and don’t introduce bugs.
As discussed in a previous blog series, automated testing can be a valuable resource when trying to deliver both agile and maintainable applications. But where should you get started and what technologies should you use to build automated tests?
In this post, I will discuss how to get started with and how to build out a simple automated test in one of the most popular options: Selenium.
Applying Bloom Filters to Java Dev: A Naive Implementation
Over the course of this blog, I will be focusing on using Bloom Filters in Java development. We’ll briefly talk through what they are and why they’re handy, and then we’ll dive into a hypothetical use case and tutorial.
As a note, this post is just meant to get you started on the track to using a Bloom Filter in the wild. What we discuss here will stay high-level but will give you a general idea of how it would work on a project.
Without further ado, let’s get started.
Tips Learned From Years of Automated End-to-End Testing
Imagine for a moment that we’re getting ready to publish a new app or feature. Following the principles of Test Driven Development (like we always do), we have created a full suite of unit tests. We’re never pressed for time, so we’ve also built out full coverage integration and functional tests.
In order to ensure our front-end is behaving as expected, we’ll need to either manually step through the application or just push our commit to the main branch and let our continuous integration pipeline do the building and testing for us. But, if we wrote our end-to-end (E2E) tests without automation in mind, we might find the results lacking in usefulness…
This post isn’t a discussion on what E2E testing is nor a tutorial on how to get started. For that, resources like Smartbear, CircleCI, and Playwright have already published articles and tutorials that do a great job of covering that ground. In this post, we’ll talk through a few tips I’ve picked up over 5 years of championing fully automated end-to-end testing.