04 / Quality & assurance
Testing that finds defects before your customers do
From test strategy to automation running in CI — I build a quality process that takes the gamble out of releases.
Defects found by customers are the most expensive kind: they cost trust, urgent fixes and the whole team's evenings. If every release makes people nervous and the list of production bugs grows faster than the list of new features, the problem usually isn't the developers. It's the missing process that catches regressions before users do.
I treat testing as engineering, not clicking through a script. Automated tests are code (Python, PyTest) wired into your CI pipeline; where automation doesn't pay off, I design manual and exploratory testing with a clearly defined scope. You don't get “more testing” — you get a deliberate process where it's clear what gets checked, when, and with what result.
My QA practice comes from projects delivered in enterprise environments — including systems connected with organizations such as PwC, Roche and E.ON, where data quality, scale and regulation leave no room for “it'll probably be fine”. I apply the same standards at every size, from a startup MVP to systems a company has relied on for years.
What the service covers
Test strategy and quality process
I work out what in your project actually needs testing and in what order: test strategy and plan, test cases and release verification rules. If a QA process already exists, I audit and improve it instead of rebuilding everything from scratch.
- Test strategy and plan for a product or release
- Test cases and checklists
- Audit and improvement of an existing QA process
- Defect analysis and triage
Test automation
I build automated test suites a team can actually maintain: UI and API tests written in Python with PyTest, running in the CI pipeline on every change. I automate what pays for itself — repeatable regression, critical paths, integration checks.
- Automated UI tests for web applications
- Automated API tests
- Regression and smoke suites in the CI pipeline (GitHub Actions)
- Taking over and cleaning up existing test suites
Manual and exploratory testing
Where automation can't see the problem, a human looks: exploratory testing of new features, release verification before production deployment, mobile app testing, and checks across browsers and devices.
- Exploratory and scripted testing of new features
- Release verification before production deployment
- Mobile app testing
- Cross-browser and cross-device testing
API, integration and database testing
I test whole flows, not just screens: API contracts between systems, end-to-end scenarios spanning several applications, and data quality in databases — consistency, completeness and migration correctness.
Performance and accessibility testing foundations
Baseline performance testing that shows how the system behaves under load and where the bottlenecks are, plus accessibility testing that catches real barriers for users. This is a foundation and a diagnosis — if a project calls for specialized performance engineering, I say so up front.
Typical situations
- 01
Every release breaks something that used to work, and the team holds its breath at each deployment.
- 02
You hear about production bugs from customers instead of from your own test process.
- 03
Your software house is growing and needs QA capacity for a project or part-time, without hiring.
- 04
There are no automated tests, and a full manual regression pass takes the team days.
What you can count on
A test process with a clear scope: what gets checked, when, and who owns it.
Automated tests running in CI on every change, so regressions surface before deployment, not after.
Readable test and defect reports that support a clear ship or don't-ship call.
Tests written like proper code: version-controlled, documented and ready for your team to take over.
Technologies
- Python
- PyTest
- REST API testing
- SQL
- GitHub Actions
- CI/CD
Questions about this service
Yes — it's a common starting point. I begin with exploratory testing and a short risk analysis: which features earn money, where defects hurt most and what has been breaking so far. That produces a priority map, and only then come test cases and automation, starting with the most critical paths.
Usually both, in different proportions. Automation pays off where the same scenarios must be repeated at every release; manual and exploratory testing works best for new features and usability. I recommend a specific mix after seeing the project, and I'm honest about where automation would not earn its keep.
Yes. I plug into your existing process and tools — the repository, the task board, the communication channels — anywhere from a few hours a week to full project involvement. I work remotely with companies across Poland, and on-site meetings are available in and around Bydgoszcz.
It is, provided it covers the right things. A small smoke and regression suite for the critical paths, running automatically in CI, can pay for itself very quickly. What I don't propose is automating everything: if maintaining a test would cost more than it's worth, I say so.
Related services
Let's talk about the quality of your releases
The first conversation is free. Tell me how testing works in your project today, and I'll propose concrete first steps — from a one-off release verification to an ongoing QA engagement.
- Phone
- +48 573 021 012