It looks soooo basic that the Spring documentation thought it deserves one single row of text – which I quote here:Continue reading
I programmed once this handy tool to retrieve one-time passwords (too much insider knowledge for opensourcing it) and as soon as some teammates heard about it, they asked for a copy to spare them the zillion clicks the password generator needs. But… the tool existed only as a Maven project in my development environment 😦
Let’s say you had this web application with nice unit tests covering the backend calculations, where people keep calling wrong calculations from the frontend. Microservices or not, it happens, so you’ll need proper integration testing. Let’s say the integration testing is a well documented but tedious two days job of clicking around. Understandably, everybody does their best to avoid it…
My answer was: how about we rewrite the integration test scenarios in the Gherkin almost-human-readable language, so we can use Cucumber to run them automated, simulating with Selenium the user browser actions! The supporting stack will be Java and Spring, actually Spring Boot, because you know all I have is a hammer….