Skip to content

Releases

NEO release history. The most recent version is listed first.

NEO v1.0.0

Stable release Β· 2026-11-03

More frameworks, your suite's conventions and authenticated sessions

NEO now generates, runs and repairs suites in Playwright + Gherkin, Cypress and Katalon Studio, and follows the organization of the suite your project already has. It can also save an authenticated session from a manual login for apps with SSO, 2FA or passkeys.


✨ New features

Playwright + Gherkin: NEO supports playwright-bdd and playwright-cucumberjs. It generates the .feature files with their steps and page objects, runs them, and repairs failures in the page object or the step without touching the scenario text.

Where: Skills β†’ lippia-neo-generate-test-suite, lippia-neo-run-and-heal Β· Adapters β†’ playwright-bdd, playwright-cucumberjs

Katalon Studio: the suite is created, run and repaired inside a Katalon Studio project through its MCP server. The bootstrap sets up the server, the location of the test cases and the browser.

Where: Skills β†’ lippia-neo-bootstrap-stack, lippia-neo-generate-test-suite, lippia-neo-run-and-heal Β· Adapters β†’ Katalon

Conventions of the existing suite: if the project already has a Lippia suite, NEO scans it and places, groups, names and tags new cases the way that suite does, instead of using a generic convention.

Where: Skills β†’ lippia-neo-generate-test-suite

Authenticated session: the new skill opens a browser, waits for a person to log in by hand (SSO, 2FA, passkey) and saves the session to reuse it in exploration and in the generated suites. It never stores or shows credentials.

Where: Skills β†’ lippia-neo-setup-authenticated-session, lippia-neo-bootstrap-stack

⚑ Improvements

Stack bootstrap: it automatically detects playwright-bdd, playwright-cucumberjs, Cypress and Katalon, and asks for the artifact folders one at a time (plans, tests, reports, manual execution and exploratory).

Where: Skills β†’ lippia-neo-bootstrap-stack

Stories by key: you can pass just the story key or ID (for example KAN-4 or US-004). NEO looks it up according to the storage configured in qa-stack.yaml (Jira, Azure DevOps or a local folder) instead of assuming it's a file.

Where: Skills β†’ lippia-neo-read-user-story, lippia-neo-resolve-user-story-source

More flexible bugs: you can provide the bug title when reading it, an acceptance criterion is no longer mistaken for a story, and a bug with no linked story is still reproduced, reporting that there is no criterion to check against.

Where: Skills β†’ lippia-neo-read-bug-report, lippia-neo-reproduce-bug

More robust CI: the GitLab, GitHub and Bitbucket pipelines install what the Playwright + Gherkin frameworks need and pin the Playwright MCP version. When there is no MR/PR (push or manual run), results are saved to one branch per source branch.

Where: Skills β†’ lippia-neo-bootstrap-ci


πŸ”„ What do I need to do?

If you have your own plans or prompts that consume the manual execution result, change findings_path to manual_execution_report_path and scenarios_executed to executed_scenarios. NEO's playbooks already use the new names.

Compatibility: the findings_path and scenarios_executed fields of the manual execution were renamed to manual_execution_report_path and executed_scenarios.

If you will use Katalon Studio, open the suite's project before generating or running tests, and manually load the global variables the bootstrap lists in the execution profile: Katalon's MCP server can't write profiles.