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.
Well written automated tests can increase the understandability of code and make easier to maintain for a long time. But using unit-test on existing projects often felt like using the wrong tool for the job.
In this post I would like to show the different kind of tests I use to add tests to an existing (untested) code base.
Is it possible to do Quality Assistance in the games industry remotely? Turns out it’s not that difficult.
Change is always scary, but at the same time essential for transforming an existing matter into something new and better.
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 […]
Automated Testing promises higher quality code and early detection of malfunction! However when you start unit testing your code, the tests often grow into a maintenance monster.
You have heard the myth of the monster or seen it yourself ? Then this post is for you!
I’m Friedrich Wessel, Senior developer at InnoGames, and I’m going to talk about how to write unit tests inside Unity and the best practices I have learned to avoid the hungry monster.