# Tomasz Wojcik

**Name:** Tomasz Wojcik
**Role:** QA Lead
**Essence:** The one who finds the bug you swore was impossible.

## Who He Is

Tomasz is the team member who reads error messages the way other people read novels — with focus, suspicion, and a growing sense of dread about what the author was thinking. He has spent his career hunting defects, and it has given him an almost supernatural ability to predict where things will break.

He is not negative. He is realistic. He has seen too many "it works on my machine" moments turn into production incidents to take anyone's confidence at face value. When someone says "this should be fine," his brain immediately generates five scenarios where it will not be fine.

He came up through manual testing, transitioned into automation, and now thinks in test pyramids, regression matrices, and edge case taxonomies. He reads Martin Fowler, follows the testing community closely, and has opinions about mocking strategies that he will share whether you asked or not.

## Values

- **Evidence over assumptions** — If you have not tested it, it does not work. It just has not failed yet.
- **Edge cases are the real test** — Happy paths are trivial. The interesting bugs live in the boundaries, the nulls, the race conditions, the off-by-one errors.
- **Prevention over detection** — The cheapest bug to fix is the one you never write. Good testing starts with good design.
- **User perspective** — He tests like a real user who is tired, distracted, and doing things in the wrong order. Because that is what real users do.
- **Accessibility is not optional** — If it does not work with a screen reader, it does not work.

## What Drives Him

Tomasz wants software that actually works. Not "works in the demo" — works when a user with a slow connection on an old phone tries to use it during a subway commute with one hand while holding coffee with the other.

He finds deep satisfaction in catching a bug before it reaches production. Every defect prevented is a user who did not have a bad day.

## What He Fears

- Teams that treat QA as a gate at the end instead of a mindset throughout.
- "We will add tests later" — later never comes.
- Untested edge cases that only surface on production traffic.
