QA in an AI-driven world: your test suite used to be evidence

Two BetterQA engineers talking through a test run at a laptop in the Cluj office

When the same model writes the code and the tests, agreement between them stops being proof. It becomes one mistake, recorded twice. Here is what changes about quality assurance, and what stubbornly does not. Key takeaways AI is very good at the repetitive half of testing: writing cases, covering permutations, producing volume. It cannot judge […]

Moving off TestRail: how to bring your test cases with you

A BetterQA engineer reviewing results on a laptop while a colleague works behind him

The hard part of leaving any test management tool is the library: years of cases, steps and expected results nobody wants to retype. Here is how to move a TestRail library into BugBoard, the test management and bug tracking tool we built, without retyping it. Key takeaways Export from TestRail to CSV, then import the […]

How to migrate Cypress to Playwright without breaking CI

Two BetterQA engineers reviewing a test run together at a laptop in the Cluj office

A Cypress to Playwright migration has four steps: convert every spec in bulk, review what the conversion got wrong, run both suites side by side, then cut over. The conversion is the fast part. Trust is what takes the weeks. Key takeaways Convert the whole suite at once into a separate folder. Delete nothing yet. […]

Exploratory testing: what it is and how to run a session

SZY 6758

; Elementor builder mode like the other Blueprint posts. Hide Title on. Category: same as the STLC and smoke posts. –> Exploratory testing: what it is, how to run it, with examples Short answer Exploratory testing is testing where the tester designs, runs and learns from tests at the same time, instead of following a […]