(This is part 2, some learnings a few weeks into the project described here: Integration tests = Cucumber + Selenium + Spring Boot)
Use the fluent wait instead of anything else, like here waiting for the expected messages to appear. Continue reading
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….
Last Friday I attended the “Software Craftsmanship and Testing” conference. I said “last Friday” because it lasted only one day, unlike the typical 3 days format (including night stays)… but for me it was just enough, I cannot really afford the extended versions. This event brought together about 50 folks with all possible backgrounds – developers .net, Java, JS, but also devops people… really, everything. The “unconference” format meant at the beginning whoever wanted to propose topics did so by placing a note on the schedule table, and explained in a few words what his discussion topic is. Continue reading