Area 13 · Development and web

Software testing and QA

Somebody will find every bug sooner or later. The only question is who: a tester on staging on a quiet Thursday morning, or a customer at the height of a sale whose BLIK payment keeps failing. We check your app, shop or portal remotely and hand back a report your developers can start fixing from the first line.

5
kinds of testing under one roof
0
site visits, all work is remote
1 ticket
= steps, data and a screenshot
PLN 190
per tester hour, excl. VAT

What one bug costs, stage by stage

A typo in a discount rule is trivial until customers hit it. The price of a fix climbs at every stage, so regular checks as work progresses are worth more than a single marathon review on the eve of sign-off.

In the specification

Almost free. You reword a sentence in the task description before any code exists.

While coding

Cheap. The developer still has the logic in mind and sorts it out in minutes.

During testing

Noticeably dearer. The ticket bounces back, and review plus staging deployment must be repeated.

After release

Expensive. An unplanned hotfix, usually in the evening, followed by anxious checks that nothing else broke.

In front of customers

Most expensive. Beyond the fix you face abandoned baskets, poor reviews on Ceneo and a flooded customer service inbox.

Automation earns back its cost only through repetition. For that reason scripts cover the settled parts of a product, the journeys nobody plans to rebuild soon. Anything still being reshaped from sprint to sprint stays manual, or your money ends up paying for script upkeep instead of new features.

What working with us looks like

You will not get a vague verdict such as “quality is average”. You get specific tickets, each with a priority. We work remotely: on your test environment, over VPN or with dedicated test accounts.

01

Understanding your system

A call on Teams or Google Meet about who uses the system, what it talks to and where an outage hurts revenue. Some screens matter far more than others, and effort follows that.

02

Agreeing the plan

Your analytics tell us which phones, browsers and journeys real visitors use, so that is what we cover. Nothing starts until you sign off the plan, including its hour budget and cost.

03

Testing and tickets

Each issue is logged straight into the tracker you already use (Jira, Azure DevOps, GitLab, GitHub) with reproduction steps, test data, expected result, a screenshot and severity.

04

Retest

When a fix is ready we confirm it works and poke at the features around it, because one repair can easily break something next door.

Questions and answers

Developers confirm their code delivers the intended behaviour. A tester hunts for situations where it does something else: an empty form, the browser back button halfway through payment, two basket tabs open at once. Those are opposite mindsets, and few people manage both towards their own work.

Yes, for example before you sign the acceptance protocol with a contractor, or before a public body formally accepts a system it ordered. We did not write the code, so we have no reason to keep quiet about anything. Testing before acceptance matters most, because that is when fixes are easiest to agree with the supplier.

Yes. Websites of local authorities, schools and other bodies covered by the Polish digital accessibility act are reviewed for WCAG 2.1 AA conformance, covering keyboard-only use, colour contrast, image descriptions and how screen readers announce the page. The European Accessibility Act, applicable since 28 June 2025, may also affect online shops; whether it covers your business is worth checking with a lawyer. The findings are useful when you update your accessibility statement.

One-off jobs are billed by the hour at PLN 190 excl. VAT, capped at the figure agreed in the test plan. Regular rounds before each release, or testing inside every sprint, are priced as a monthly flat fee so you know the cost in advance. VAT invoices go out through KSeF.

Ideally there is none. We suggest synthetic records or an anonymised copy of the database. Where production records cannot be avoided, a GDPR data processing agreement is signed first, and access to the data is kept to the minimum needed.

Let us find the bugs before your customers do

Tell us what needs testing and when you plan to launch. We will send back a test plan and a quote based on the number of scenarios.

Hours
Mon-Fri 8:00-18:00 CET, reply within one working day
Meetings
Online via Teams or Google Meet

We set strictly necessary cookies only: they keep the site running and remember the city you chose. Nothing here is used for advertising or tracking. More in our privacy policy.