TypeScript icon, indicating that this package has built-in type declarations

3.6.4-beta.2 • Public • Published

Stand With Ukraine

NPM version AI features StandWithUkraine

Build Status:

Appium Helper: Appium V2 Tests - Android Appium V2 Tests - iOS

Web Helper: Playwright Tests Puppeteer Tests WebDriver Tests TestCafe Tests

CodeceptJS Made in Ukraine

Reference: Helpers API

Supercharged E2E Testing

CodeceptJS is a new testing framework for end-to-end testing with WebDriver (or others). It abstracts browser interaction to simple steps that are written from a user's perspective. A simple test that verifies the "Welcome" text is present on a main page of a site will look like:

Feature('CodeceptJS demo');

Scenario('check Welcome page on site', ({ I }) => {

CodeceptJS tests are:

  • Synchronous. You don't need to care about callbacks or promises or test scenarios which are linear. But, your tests should be linear.
  • Written from user's perspective. Every action is a method of I. That makes test easy to read, write and maintain even for non-tech persons.
  • Backend API agnostic. We don't know which WebDriver implementation is running this test.

CodeceptJS uses Helper modules to provide actions to I object. Currently, CodeceptJS has these helpers:

  • Playwright - is a Node library to automate the Chromium, WebKit and Firefox browsers with a single API.
  • Puppeteer - uses Google Chrome's Puppeteer for fast headless testing.
  • WebDriver - uses webdriverio to run tests via WebDriver or Devtools protocol.
  • TestCafe - cheap and fast cross-browser test automation.
  • Appium - for mobile testing with Appium
  • Detox - This is a wrapper on top of Detox library, aimed to unify testing experience for CodeceptJS framework. Detox provides a grey box testing for mobile applications, playing especially well for React Native apps.

And more to come...

Why CodeceptJS?

CodeceptJS is a successor of Codeception, a popular full-stack testing framework for PHP. With CodeceptJS your scenario-driven functional and acceptance tests will be as simple and clean as they can be. You don't need to worry about asynchronous nature of NodeJS or about various APIs of Playwright, Selenium, Puppeteer, TestCafe, etc. as CodeceptJS unifies them and makes them work as they are synchronous.


  • 🪄 AI-powered with GPT features to assist and heal failing tests.
  • ☕ Based on Mocha testing framework.
  • 💼 Designed for scenario driven acceptance testing in BDD-style.
  • 💻 Uses ES6 natively without transpiler.
  • Also plays nice with TypeScript.
  • </> Smart locators: use names, labels, matching text, CSS or XPath to locate elements.
  • 🌐 Interactive debugging shell: pause test at any point and try different commands in a browser.
  • Easily create tests, pageobjects, stepobjects with CLI generators.


npm i codeceptjs --save

Move to directory where you'd like to have your tests (and CodeceptJS config) stored, and execute:

npx codeceptjs init

to create and configure test environment. It is recommended to select WebDriver from the list of helpers, if you need to write Selenium WebDriver tests.

After that create your first test by executing:

npx codeceptjs generate:test

Now test is created and can be executed with

npx codeceptjs run

If you want to write your tests using TypeScript just generate standard Type Definitions by executing:

npx codeceptjs def .

Later you can even automagically update Type Definitions to include your own custom helpers methods.


  • CodeceptJS requires Node.js version 12+ or later.


Learn CodeceptJS by examples. Let's assume we have CodeceptJS installed and WebDriver helper enabled.


Let's see how we can handle basic form testing:

Feature('CodeceptJS Demonstration');

Scenario('test some forms', ({ I }) => {
  I.fillField('Email', '');
  I.fillField('Password', secret('123456'));
  I.checkOption('Male');'Create User');
  I.see('User is valid');

All actions are performed by I object; assertions functions start with see function. In these examples all methods of I are taken from WebDriver helper, see reference to learn how to use them.

Let's execute this test with run command. Additional option --steps will show us the running process. We recommend use --steps or --debug during development.

npx codeceptjs run --steps

This will produce an output:

CodeceptJS Demonstration --
 test some forms
 • I am on page ""
 • I fill field "Email", ""
 • I fill field "Password", "****"
 • I check option "Active"
 • I check option "Male"
 • I click "Create User"
 • I see "User is valid"
 • I dont see in current url "/documentation"
 ✓ OK in 17752ms

CodeceptJS has an ultimate feature to help you develop and debug your test. You can pause execution of test in any place and use interactive shell to try different actions and locators. Just add pause() call at any place in a test and run it.

Interactive shell can be started outside test context by running:

npx codeceptjs shell


We filled form with fillField methods, which located form elements by their label. The same way you can locate element by name, CSS or XPath locators in tests:

// by name
I.fillField('user_basic[email]', '');
// by CSS
I.fillField('#user_basic_email', '');
// don't make us guess locator type, specify it
I.fillField({css: '#user_basic_email'}, '');

Other methods like checkOption, and click work in a similar manner. They can take labels or CSS or XPath locators to find elements to interact.


Assertions start with see or dontSee prefix. In our case we are asserting that string 'User is valid' is somewhere in a webpage. However, we can narrow the search to particular element by providing a second parameter:

I.see('User is valid');
// better to specify context:
I.see('User is valid', '.alert-success');

In this case 'User is valid' string will be searched only inside elements located by CSS .alert-success.


In case you need to return a value from a webpage and use it directly in test, you should use methods with grab prefix. They are expected to be used inside async/await functions, and their results will be available in test:

Feature('CodeceptJS Demonstration');

Scenario('test page title', async ({ I }) => {
  const title = await I.grabTitle();
  I.expectEqual(title, 'Example application with SimpleForm and Twitter Bootstrap'); // Avaiable with Expect helper. ->

The same way you can grab text, attributes, or form values and use them in next test steps.


Common preparation steps like opening a web page, logging in a user, can be placed in Before or Background:

const { I } = inject();

Feature('CodeceptJS Demonstration');

Before(() => { // or Background

Scenario('test some forms', () => {'Create User');
  I.see('User is valid');

Scenario('test title', () => {
  I.seeInTitle('Example application');


CodeceptJS provides the most simple way to create and use page objects in your test. You can create one by running

npx codeceptjs generate pageobject

It will create a page object file for you and add it to the config. Let's assume we created one named docsPage:

const { I } = inject();

module.exports = {
  fields: {
    email: '#user_basic_email',
    password: '#user_basic_password'
  submitButton: {css: '#new_user_basic input[type=submit]'},

  sendForm(email, password) {
    I.fillField(, email);
    I.fillField(this.fields.password, password);;

You can easily inject it to test by providing its name in test arguments:

Feature('CodeceptJS Demonstration');

Before(({ I }) => { // or Background

Scenario('test some forms', ({ I, docsPage }) => {
  I.see('User is valid');

When using Typescript, replace module.exports with export for autocompletion.



Thanks all to those who are and will have contributing to this awesome project!


MIT © CodeceptJS Team

Package Sidebar


npm i codeceptjs


Weekly Downloads






Unpacked Size

2.12 MB

Total Files


Last publish


  • davert
  • alex_vorobey
  • thanh.nguyen
  • egor_bodnar