Generate and Maintain CodeceptJS End-to-End Tests

CodeceptJS Test Expert Agent writes end-to-end test suites with CodeceptJS's BDD syntax: page objects for maintainable UI interactions, configuration for the Playwright and REST helpers, well-structured Scenario/Feature tests with tags and data-driven scenarios, custom actor steps, and combined API-plus-UI consistency checks.

Use it when writing or extending CodeceptJS end-to-end tests - configuring codecept.conf.js with Playwright and REST helpers and plugins, building a Page Object Model for a UI flow, writing tagged smoke, negative, or data-driven scenarios, adding custom actor steps for shared actions, or combining an API call with a UI assertion in one scenario. It's specific to CodeceptJS - its semantic methods (I.see, I.click, I.fillField), actor-based custom steps, and plugin configuration don't transfer to other frameworks like Playwright's own test runner or Cypress.

Input is the feature or user flow to test and the helpers already configured, such as Playwright, WebDriver, or REST. Output is CodeceptJS code: a codecept.conf.js with a Playwright helper (headless toggle, timeouts), a REST helper for API calls, screenshotOnFail and retryFailedStep plugins, and page-object includes; a LoginPage page object with locators, a login action, and an error-verification helper; tagged scenarios covering a smoke-tagged successful login, a negative-tagged invalid-credentials case, and a Data-driven scenario running the same login across multiple users; a custom steps_file.js actor with a loginAsAdmin shortcut, a waitForAPIResponse helper that waits on both the request and response, and a verifyTableContains assertion over grabbed table text; and a combined API-plus-UI scenario that fetches a user's profile via I.sendGetRequest and asserts the same data renders on the page.

Built on CodeceptJS with the Playwright and REST helpers, @codeceptjs/configure for headless mode, Mocha for the codeceptjs-cli-reporter, and support for WebDriver as an alternative browser helper:

  async login(email, password) {
    I.fillField(this.fields.email, email);
    I.fillField(this.fields.password, password);
    I.click(this.buttons.login);
    I.waitForNavigation();
  },

It also covers debugging support - pause() for interactive debugging, I.say() to log test steps, and I.saveScreenshot() at critical checkpoints - plus performance tips like minimizing page reloads between related scenarios and caching authentication state to avoid re-logging in on every test, plus running independent test suites in parallel rather than serially.

QA engineers and developers building CodeceptJS test suites who want the framework's own best practices applied - Page Object Model, semantic locators over XPath, data-testid selectors, semantic waits instead of hard-coded delays, proper test isolation, cached authentication state via I.saveStorageState(), and investigating flaky tests instead of ignoring them.