(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….
One problem I have when trying new technologies is actually seeing them in realistic situations – which translates to having a real use case for them. Think about this: when you build a “hello world” application you actually couldn’t be further away from the real world! I guess that’s why nobody calls it “hello real world” anyway… The whole experience you get from the proof of concept is just random installation trivia if you’re not using it to prove a point. That’s why it’s called “proof of concept” – it should have a concept, silly. Continue reading
…but web frameworks are today ten a penny, why would I be still looking for something? Could it be I didn’t look around enough? Am I too finicky? Or blind for not seeing it right in front of me? Whatever, fact is I’m still looking for the „perfect“ web framework. It doesn’t have to be REALLY new – but it certainly would be new to me.
I would like it to be, in no particular order: Continue reading