Retro of the week #17 Automation for Automation sake
On Sunday it will be the month since I came back in Poland I am still not fully unpacked, but I am operational. And It means another weeks retro. Including question about…
Flower VI – Naming is still important
I am a firm believer in self-documenting code so if you see a code and you see the comment; it means something is wrong. Yes, there are exceptions to the…
Flower V – I don’t even know how to call it.
This post is part of longer series about code smell and antipatterns in tests automation you can see more here. Today we will take a look at abuse of try…
Flower 4: Unused Code
This post is part of longer series you can see more here There are many bad practices that you can observe in the test code. Some of them are minuscule…
Flower 3: Who needs SRP anyway
Single Responsibility Principle is one of the core guidelines for object-oriented programming. In short, it means one class has does one thing only. Same for methods it does exactly one…
Meetup: When machines lie to us and why manual testing is still needed
On Wednesday I was speaking at Dublin Ministry of Testing Meetup. I have given few presentations already, but that was my first in English. I was excited, and to rise…
Flower 2: Wet Useless If Statement
The following post is part of series called 'Flowers.' You can find a previous entry here: Flower 1 Wet Locators This time we start with this masterpiece of an if statement.…
Flower 1: WET Locators
Flower Series Introduction In Poland, stories about some silly mistake that you or someone else has made are called flowers. Probably after THE LITTLE FLOWERS OF SAINT FRANCIS OF ASSISI.…