Attention: This article was published over 2 years ago, and the information provided may be aged or outdated. While some topics are evergreen, technology moves fast, so please keep that in mind as you read the post.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. …
Attention: This article was published over 2 years ago, and the information provided may be aged or outdated. While some topics are evergreen, technology moves fast, so please keep that in mind as you read the post.How often in Java services do we need to use the current date and time? Most of us would agree we use it quite …
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.
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.
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.