2.4 Converting Manual Test Cases into Automated CertiQA Tests

A practical framework for manual QA testers to convert test scripts, Excel matrices, or Jira tickets into automated tests.

Manual Steps Already Speak CertiQA’s Language

Most manual regression scripts and Jira test steps are already written in an implicit action vocabulary – “open the page,” “enter a value,” “click a button,” “verify the result” – testers just don’t usually think of it that way. CertiQA’s visual blocks are built around that exact same vocabulary, so converting a manual script isn’t really a translation exercise: it’s closer to re-typing the same steps into a different, executable format. A tester moving from a spreadsheet test matrix or a numbered Jira checklist doesn’t need to learn Playwright, a selector syntax, or async timing to get started – they need to learn which row in the table below their next manual step maps to.

Manual Test Step	CertiQA Action	How to Configure on Canvas
Open web application	LAUNCH	Enter URL in target field.
Enter username in text box	TYPE	Target element by text label, value = {{ username }}.
Click “Sign In” button	CLICK	Select CLICK, target button element.
Verify dashboard appears	ASSERTION (VISIBLE)	Target #dashboard or text=“Welcome”, verification=VISIBLE.

Beyond the One-to-One Mapping

A handful of manual steps don’t reduce to a single block, and recognizing them while converting is what turns a batch of one-off cases into a suite that stays maintainable afterward. “Repeat login as three different roles” is really the same short LAUNCH -> TYPE -> TYPE -> CLICK sequence pulled into a CertiBlock and reused with a different variable value per case, rather than copied three times. “Skip this step if the promo banner is showing” is a conditional IF branch (ELEMENT_EXISTS) on the CLICK step, rather than a judgment call the tester used to make silently in their head.

Converting a Batch Efficiently

• Convert the login/setup steps once as a CertiBlock, then build every downstream case on top of it – a password-field rename then only needs fixing in one place, not in every converted case.
• A value a manual tester would type by hand – a test email address, today’s date – is usually a better fit for a dynamic macro ({{ $randomEmail }}, {{ $timestamp }}) or a variable than a literal string baked into the step; it’s the difference between a test that still passes next month and one that starts colliding with itself.