
How We Built Our Own TestBench
...and why you don't need a whole microscope just to test firmware
Go to content|Go to the main menu|Go to search
A software tester is a person who likes to tinker with anything and everything, figure things out, and leave no unanswered questions behind. What can you expect from a software tester as a partner?
A product owner could mean a customer. This is someone who should have an idea of how something should look and work. A tester can prepare an analysis, evaluate risks, bring validation data and propose solutions.
Not that testers would not be able to make decisions on their own, but they focus on making sure that everything is transparent and "sanctified" by all stakeholders. So be prepared to take responsibility for the decision.
Are you buying a house and choosing among several properties? Forget that the tester will decide based on the view. Rather, expect the tester to prepare a decision table where the view will have a lower priority. On the other hand, the tester will assign a higher priority to "parameters" such as accessibility to public transport, distance from the district town, number of schools in the neighborhood, or opening hours of a convenience store. Feelings aside, the data decide!
A tester is actually a developer, a programmer, an IT guy. You must have heard of them. There are a lot of myths and half-truths about this strange species. It should be stated that some of them are true.
Unlike communication between "normal" people, we IT professionals think partly in source code, machine-like. There is therefore no room for guesses, unspoken presumptions, and double interpretations. Let’s simplify this, be prepared that your partner will sometimes talk like a machine, and will expect the same from you. Keep things short and clear.
The wife sends the programmer shopping. Buy ten rolls and when they have eggs, buy 30. The programmer comes into the store and says: "Do you have eggs?" "Yes, we do," replies the clerk. "30 rolls, please."
It might be useful to learn the basics of programming:
from shop import ShoppingCart, Stock
from food import Roll, Egg
shopping_basket.add_item(Roll, 10)
if Stock.eggs.is_available():
shopping_basket.add_item(Egg, 30)
You don't have to worry about partnering with a tester. We're only human too. Although a little weird.

How does organizing a game jam work, from the initial steps all the way to the final awards ceremony? How did our game jam differ from traditional ones, and why is hosting a game jam at a company actually a fantastic idea?

Every project that uses LLMs for generating code, tests, or documentation should include some kind of harness – a set of rules that defines how the agent should behave. Unfortunately, the configuration of these rules is still inconsistent; the individual cloud AI tools (Copilot, Codex, Claude) each use different formats. Our team is made up of people from different organizations, so we set out to create a harness that would be common to all tools and lead to similar agent behavior.
Thank you for your interest in subscribing to our newsletter! To complete your registration you need to confirm your subscription. We have just sent you a confirmation link to the email address you provided. Please click on this link to complete your registration. If you do not find the email, please check your spam or "Promotions" folder.
