How we work

Honza and Jana ensure that Tesena wins new contracts, pushes long-term partnerships, and provides Teseners with growth opportunities. Their main mission is simply to make sure that we work well with our clients. They are in daily contact with clients. That's why we interviewed them to find out what the main benefits of working with Tesena are and why it's worth doing testing in the first place.

Why Tesena?

Honza: Because Tesena is not just a service provider. We go beyond that. When we work together, we become partners who are part of the project team, and our involvement is not just about spinning the speedometer for 8 hours a day. Often we are so close to the project that we can perceive and support the problem before it arises. When a complication does arise, we don't bury our heads in the sand, but actively seek a solution.

Jana: The most important thing for us is the relationship with the client and the fact that we can rely on each other. What we agree on is valid, we have common goals and we trust each other. Not every project goes smoothly, but we always try to help the client as much as possible so that their experience of working with us is as positive as possible and they know they can trust us. Which is the principle on which Tesena operates as a whole, not just on an individual level.

Why testing? Some might say it's an unnecessary expense...

Honza:  Nonsense. Show me one thing in the world that's perfect as soon as it's created. That's doubly true for something that's man-made. Humans naturally make mistakes, and if you want to have the best software development team, you have to have a tester on it who is able to find the most critical bugs before your users find them. And believe me, the cost of such a person is certainly less than fixing a major bug in a product that is already in use.

Jana: That's something that's usually said by people who haven't dealt with a crisis over an undiscovered production bug. Testing is often only appreciated when we lose clients and business, when we lose trust, simply when there is a problem. And then testing can be really unnecessarily expensive. Yet it doesn't just serve a preventive function. In fact, a tester's insight can significantly improve the efficiency of the product development process itself or its subsequent maintenance and development.

Can you think of an example of a specific situation where a client was delighted to have ordered testing?

Honza: We had a client who had fundamentally underestimated the role of testing within the SDLC and had devoted most of their budget to development and analysis. At the last minute, he decided to at least partially test the delivered system and found that the application under development was nowhere near ready for a production environment. By doing at least basic testing, he saved more than €3 million in roll-back and rework that would have followed a production roll-out, not to mention the far more fundamental problem of loss of credibility with end users. This was one of those situations where the customer realizes that testing is not an unnecessary expense...

Jana: He may not have been thrilled about ordering testing, but he was glad he ordered it from Tesena. Because he saw that there was another way to do it. Tesena can work efficiently with its people—within a short time, they can quickly navigate and adapt to new conditions to meet and often exceed expectations. We can afford to nominate consultants to a client's team primarily because of close collaboration, trust, and understanding.

Jan Stehlík
Head of Business Development
Jana Šmehýlová
Sales and Account Manager