Before starting Nika Studio I worked for two years as a QA Engineer, the only person responsible for quality on a mobile app for iOS and Android, with its backend and admin dashboard. My job was to find what was broken before the user did. Now I build websites, and that way of looking at software has stayed with me.
Test cases as the exit gate
In that team, a task only moved forward when all its test cases were green. Today I do the same with my own code: before calling something finished, I define what has to happen and in which cases it must not break.
Thinking about the user who leaves the happy path
As a QA I learned that bugs do not show up when everything goes well, but with an empty field, an odd value, a small phone or a slow connection. That is why I validate everything that reaches the server, test websites on mobile and check accessibility.
Automating what repeats
A manual regression before every release is expensive and ends up being skipped. In my projects, every change automatically goes through a pipeline with unit tests, API tests, end-to-end tests with Playwright and accessibility checks with axe. If something breaks, I find out before the client does.
A well-reported bug is half solved
Steps to reproduce it, what was expected and what happened, evidence. I apply this now when a client tells me about something: first I reproduce it, then I fix it, and finally I add a test so it does not come back.
What the client gets
Websites that do not just work on delivery day, but keep working when they change, because every change goes through the same checks.
