While developing a game it’s often required to have a player in a certain state. Especially when testing new features or bug fixes.
In a previous blog post I introduced you to our player setup system for backend integration tests. In this post I will explain how the frontend can use the same system without any additional effort!
Tests should be easy to read and fun to write! In our daily business, we add new features and do refactoring or bug fixes. Every change could lead to a failing test. If we look at the failed test, we should immediately be able to understand what the test is doing. But often enough this is not the case.
In this post I will show you how we improved the readability and maintenance effort of our tests by introducing a builder-like API to prepare the test scenario.
When the requirements are given for a piece of software, they usually cover only a minor section of what the software should do and be. Aspect-Oriented Programming (AOP) provides a way to think about all the necessary, but not easily compartmentalized components of a software system.
If you have been working as a developer for a while, you will almost certainly have come across legacy code. And you probably hated working on it. It is code that has been working fine the way it is for long enough that most of – if not all – the developers in your team […]
In this post we’ll go through an example application and see which methods and principles we can apply to build a robust application that is easy to maintain, extend, understand and use. In general, this is a subject with a much larger scope than a simple blog post can provide, so the content is neither […]