Gaining enough visibility on what’s going on in your services can be a struggle. Here I will show how distributed tracing can help with that and what some of the benefits are that we encountered while implementing it.
INNOGAMES STORIES

Testing iOS In-App Purchases
Testing in-app purchases can be a challenge, especially if you want to cover edge cases.
In this blog post, I discussed some of the difficulties we faced with the in-app purchase tests for iOS and an easier way to simulate payments without App Store Connect.

Testing Jenkinsfiles and Libraries
Jenkins is an open source continuous integration server to automate build, test and deploy pipelines and even more. Jenkins pipelines and libraries have a big benefit as they can be added to SCM. However, testing of pipelines and libraries can be a hassle sometimes, especially when not dealing with it on a daily basis. One […]

The Player Setup Endpoint – Let the Frontend run Backend code
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!

What is Software Testing?
To err is human. No matter how much of a perfectionist we are, we are all bound to make mistakes. Software testing can help prevent and discover mistakes in software development. If you’d had to answer “What is software testing?” what would you say? For me it is something pretty difficult to compress into a […]

Shaping your Testing Pyramid through test case selection
You have probably stumbled upon the concept of the Testing Pyramid at some point… It highlights the value of testing, but even more so the importance of knowing where and how to test. We want our tests to cost less and the results to be fast. How should we accomplish this? Let’s find out together!

How to make your tests more readable and maintainable
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.

Bring Light into Darkness – How to add tests to an existing project
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.

Doing Quality Assistance Remotely
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.

How we Rewrote Wallet Using Test Driven Development
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 […]