Oct 22, 2020
In two previous posts we discussed the benefits of automated tests and the properties of a good test. So far we were trying to avoid differentiating the tests in any way. This time we want to address one way how tests can be classified: tests granularity.
Anatomy of a Good Test
Sep 23, 2020
In our last post, we focused on why we should write tests and what value they provide. This time we will go far more technical and take a look at a single test. We will show what makes a test a good one and describe desired and unwanted properties. Interestingly enough, all those properties hold, no matter how isolated or integrated the test is. This already gives us a hint that all tests are alike, we should remember that. Unfortunately, as the topic is very broad, we will have to skip some aspects that play a role when we’re talking about test suites. We will get back to them in one of our next posts.
Why You Should Write Automated Tests
Aug 27, 2020
This blog post gives an overview of the most common benefits gained by writing automated tests. It starts in a place where most of the projects we’ve seen so far are: tests are written as a last step of the development process. Then it shows additional benefits that could be gained if we all gave the tests a bit more focus and care.
Iteration 9 - custom functions
Aug 24, 2020
In WebCalc's ninth iteration I'm enabling users to define their own functions
Familiarity - friend or foe
Oct 8, 2019
Familiarity has two sides. On one, it is quite beneficial, you know the ways, the tools, the pitfalls and it all enables you to work fast. But at the same time, it can make you blind to mistakes you're doing or violations of processes or good practices.
Iteration 8 - billing module extraction and differentiating users
May 13, 2019
In WebCalc's eighth iteration I'm fixing mistakes I made previously while trying, at the same time, introduce differentiation of users - bad idea.
Iteration 7 - billing
Apr 8, 2019
WebCalc's seventh iteration is all about billing basic four operations and making them visible in the balance.
Iteration 6 - introducing users
Mar 28, 2019
WebCalc sixth iteration. I'm introducing users, so that I can start billing them for using my CPU time. That forces me to include Spring Security in the project.
Iteration 5 - more complex calculations
Dec 18, 2018
In WebCalc's fifth iteration I'm adding support for more complex calculations. I'm also finally dealing with dependency management.
Iteration 4 - fixes only
Nov 2, 2018
WebCalc's fourth iteration is mostly about fixing issues, big and small. First, I'm making my Calculator stateless. Then I'm fixing all issues related to number formatting, especially input parsing.