As discussed in a previous blog post, Selenium is a popular choice for automation testing, and when you pair it with Cucumber, you unlock even more benefits. By writing test cases in Cucumber’s human-readable format, teams can improve clarity, boost maintainability, and make collaboration easier — even for non-technical stakeholders. In this post, I’ll walk you through how to integrate Cucumber with Selenium to create efficient, effective tests that set your team up for success.
In my last post, “Introduction to Web Apps with Next.js”, we went through the steps of setting up a new Next.js project, customizing a landing page, and implementing a very simple web application. In this post, we’ll implement an Open Authentication (OAuth) based Single Sign-On (SSO) API within Next.js using NextAuth.js. We’ll be using GitHub as our provider, but the steps here are very similar for other platforms, such as Google or Discord. This will allow us to place portions of our website behind a login screen, restricting access to certain content or APIs for anonymous visitors.
Test coverage is a metric that measures how much of your codebase is exercised by tests, providing insight into the effectiveness of your testing efforts. In this blog, we’ll focus on API projects, exploring the types of tests suited for code coverage, realistic goals (and tools to help achieve them), and the minimum coverage needed to reap the benefits of your tests.
Testing your code—down to individual lines—is a critical practice in modern software development. It helps ensure applications remain reliable, stable, and maintainable, all while balancing practical constraints.
The world of technology is constantly evolving, but despite the rise of cutting-edge programming languages and modern software frameworks, COBOL applications continue to play a critical role in the business world. COBOL, one of the oldest programming languages, still powers many of the core systems of industries like banking, insurance, and government. Why, then, are businesses increasingly considering modernizing COBOL …
While working with a client a few years ago, I was introduced to the concept of a Software Bill of Materials, colloquially known as an SBOM. It didn’t take long before I recognized its immense value and importance in improving security and integrity in software development. Hopefully, over the next few minutes as you read this blog, you’ll start to see that as well.
The topic of SBOMs has become more and more popular over the past several years and is increasingly critical in this technology-driven world. We’ve all heard of numerous enterprise-level data attacks, exposures, and leaks in recent years, and almost all are caused by some sort of security vulnerability. Many of these incidents could have been realized and possibly even mitigated before disaster struck if an SBOM had been in play.
