← all publishers

codeceptjs

@codeceptjs source repo

13 published skills

  1. CI Fix Tests · codeceptjs
    Use on CI in non-interactive mode after a failed CodeceptJS run — attempts safe fixes only (locator drift, missing waits), reruns failing scenarios, rolls back edits that didn't help, reports at `output/ci-fix.md`. No refactors, no config edits, no flake-masking. Trigger on "ci fix tests", "auto-fix failing tests", "attempt repair on CI", or as a CI step after a failed run.
    0
    installs
  2. Codeceptjs Auth · codeceptjs
    Use when a CodeceptJS test needs login, user roles, or session reuse — or when another CodeceptJS skill identifies authorization is required. Also on auth-related test failures. Trigger on login, sign-in, sign-up, authentication, sessions, "logged in", admin/editor/user roles.
    0
    installs
  3. Migrate Codeceptjs 4 · codeceptjs
    Migrate a CodeceptJS 3.x project to 4.x. Trigger when `package.json` pins `codeceptjs` at 3.x or is missing `"type": "module"`, when test files still use CommonJS (`require()` / `module.exports`) against CodeceptJS APIs, when config references removed helpers (`Nightmare`, `Protractor`, `TestCafe`, `AI`, `SoftExpectHelper`, `Mochawesome`) or removed plugins (`autoLogin`, `tryTo`, `retryTo`, `eachElement`, `commentStep`, `fakerTransform`, `enhancedRetryFailedStep`, `allure`, `htmlReporter`, `wdio`, `selenoid`, `screenshotOnFail`, `pauseOnFail`, `stepByStepReport`), or when 3.x APIs are in use (`ai.request` function, Joi schemas in `seeResponseMatchesJsonSchema`, `restart: 'browser'`, `I.retry()`, `I.limitTime()`, Playwright `customLocators`).
    0
    installs
  4. Codeceptjs Exploration · codeceptjs
    Use when an agent needs to learn what's on a page in CodeceptJS — read the ARIA tree, inspect candidate elements, pick or disambiguate a stable locator. Drives the live browser via MCP `run_code` / `snapshot`. Invoked by writing-codeceptjs-tests, debugging-codeceptjs-tests, and refactoring-codeceptjs-tests whenever page inspection is needed.
    0
    installs
  5. Codeceptjs Fundamentals · codeceptjs
    Run first when working with any CodeceptJS 4 project — before writing, debugging, refactoring, or migrating tests. Teaches the framework's non-obvious rules and runs four-step discovery (`check` → read config → `list` → `dry-run`) reporting which helpers, plugins, page objects, custom actions, and tests are active. Other CodeceptJS skills depend on this output.
    0
    installs
  6. Codeceptjs Run Analysis · codeceptjs
    Use after running CodeceptJS tests with the `aiTrace` plugin enabled and the results need review — verify a fix held, investigate a single failure, cluster errors across a CI fail-storm, diagnose flakiness across reruns. Invoked by other CodeceptJS skills whenever a run has happened. Trigger on "what failed", "analyse the run", "cluster these errors", "is it flaky", "did the fix hold".
    0
    installs
  7. Writing Codeceptjs Tests · codeceptjs
    Use when creating a new CodeceptJS 4 test, extending an existing Scenario, or porting a manual test plan to code. Builds tests against the live browser via the CodeceptJS MCP server — never from imagined locators or flows. Trigger on any request to create, write, add, draft, or scaffold a CodeceptJS test, login flow, end-to-end check, or "test from scratch".
    0
    installs
  8. Debugging Codeceptjs Tests · codeceptjs
    Use when a CodeceptJS 4 test fails, flakes, or behaves unexpectedly. Trigger on run errors and stack traces from `npx codeceptjs run`, intermittent failures, locator drift, timing issues, "works locally fails in CI", "why does this fail", trace/screenshot/console mentions, and breakpoint / step-through / "pause at step N" requests.
    0
    installs
  9. Refactoring Codeceptjs Tests · codeceptjs
    Use when cleaning up existing CodeceptJS 4 tests — deduplication, extracting page objects, taming long locators, moving raw JS into custom helpers. Targeted (one file) or global (whole tests directory); always proposes before applying. Trigger on "refactor my tests", "clean up", "extract page object", "this test is too long", "deduplicate", or when reviewing test files for quality.
    0
    installs
  10. Migrate Cypress To Codeceptjs · codeceptjs
    Port a Cypress test suite to CodeceptJS 4. Trigger when the project contains `cypress.config.{js,ts,mjs}`, a `cypress/` directory (`cypress/e2e/`, `cypress/support/{commands,e2e}.*`, `cypress/fixtures/`), `cypress` in `devDependencies`, or test code calling `cy.*` (`cy.visit`, `cy.get`, `cy.contains`, `cy.session`, `cy.intercept`, `cy.request`, `cy.task`, `cy.fixture`, `cy.origin`, `cy.mount`), `Cypress.Commands.add(...)`, or `Cypress.env(...)`.
    0
    installs
  11. Migrate Testcafe To Codeceptjs · codeceptjs
    Port a TestCafe test suite to CodeceptJS 4. Trigger when the project contains `.testcaferc.{json,js,ts,cjs}`, `testcafe` in `devDependencies`, test files importing from `testcafe` (`Selector`, `ClientFunction`, `Role`, `RequestMock`, `RequestHook`, `RequestLogger`), top-level `fixture('X').page(...)` + `test('y', async t => { ... })` blocks, `Selector(...)` chains (`.withText`, `.nth`, `.find`, `.filter`), `await t.click(...)` patterns, `t.useRole(...)`, `t.eval(...)` / `ClientFunction(...)`, or TestCafe Studio recordings.
    0
    installs
  12. Migrate Protractor To Codeceptjs · codeceptjs
    Port a Protractor test suite to CodeceptJS 4. Trigger when the project contains `protractor.conf.{js,ts}`, `protractor` in `devDependencies`, `*.e2e-spec.{js,ts}` files, an `e2e/` (or `protractor/`) directory with spec files, `@types/jasmine` / `jasmine-spec-reporter` in dependencies, imports from `protractor` (`browser`, `element`, `by`, `ExpectedConditions`), or code calling `element(by.X(...))`, `element.all(...)`, `by.addLocator(...)`, `browser.get(...)` / `browser.executeScript(...)` / `browser.wait(EC.*)` / `browser.waitForAngular(...)` / `browser.ignoreSynchronization` / `browser.params.*`.
    0
    installs
  13. Migrate Selenium Java To Codeceptjs · codeceptjs
    Port a Selenium WebDriver or Selenide (Java) test suite to CodeceptJS 4. Trigger when the project contains `pom.xml` declaring `selenium-java` / `selenide` / `webdrivermanager` / `junit-jupiter` / `testng`, a `build.gradle{,.kts}` with `org.seleniumhq.selenium` / `com.codeborne:selenide`, a `src/test/java/` tree with `*Test.java` / `*IT.java` / `*Steps.java`, imports from `org.openqa.selenium.*` (`WebDriver`, `By`, `WebDriverWait`, `ExpectedConditions`, `Actions`) or `com.codeborne.selenide.*` (`Selenide`, `SelenideElement`, `Condition`), JUnit/TestNG annotations (`@Test`, `@BeforeEach`, `@DataProvider`, `@FindBy`, `@ParameterizedTest`), `PageFactory.initElements(...)`, `new ChromeDriver(...)` / `Selenide.open(...)`, or Cucumber-JVM step defs (`@Given` / `@When` / `@Then`).
    0
    installs