12 Program Challenge update #7 4th Task Done!
Time flyes and January is coming to an end.So let's see how well I did on project four went. The Excuses I will admit. This exercise was simple cause I…
Interface For help (c#)
This short article is a small case study with two main points: The usefulness of interface with Generics and the consequences of the decision made in planning automation. The issue…
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…
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.…
Clean Code by Robert C. Martin from Tester Perspective
TL;DR [expand = "Click here to see short summary"] Good Book! It will help you shape how to think about writing code, even for test automation. [/expand] A struggle for quality…