Gerhard Lausser avatar

Gerhard Lausser

Community

@lausser · Munich, Germany

118Followers
|
105Public Repos
|
3Published Skills

I will ignore all of your mails unless you give me an ip address and a community/root account. No joke! No exception!

Skills Distribution
DomainDeveloper To...Browser Test Migra.. (35%)Visual UI Test Loc.. (30%)Playwright Test Au.. (25%)Test Quality Gates (10%)

Agent Skills by Gerhard Lausser

Showing 3 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Gerhard Lausser

FAQPage Schema
What tasks can I accomplish with Gerhard Lausser's skills?

You can migrate Sakuli v1/v2 browser tests to Playwright in the check_cep container, translate Sahi DOM selectors, preserve SikuliX image steps as check-cep-vision calls, write visual template-matching tests, and author deterministic check_cep tests from plain-language intent files.

Who should use these Sakuli and check_cep testing skills?

QA engineers and test developers maintaining legacy Sakuli or Sahi suites who need to modernize to Playwright, plus teams building vision-based UI tests where DOM selectors are unreliable and image template matching with hybrid fallback is required.

How does the cep-test-authoring skill work in practice?

It takes a plain-language intent file (*.ai), explores the target site to find stable locators, records site knowledge in KNOWLEDGE.md, and produces a deployable check_cep Playwright test that must pass the authoring quality gate, critic pass, and VERIFICATION.md.

What are the prerequisites for using these skills?

You need the check_cep container environment for running migrated Playwright tests, existing Sakuli v1/v2 scripts for migration work, and an intent file describing the user flow when authoring new tests with cep-test-authoring.