codeceptjs 3.2.3 → 3.3.0-beta.1

package/docs/plugins.md

@@ -58,6 +58,21 @@ const allure = codeceptjs.container.plugins('allure');
 -   `addAttachment(name, buffer, type)` - add an attachment to current test / suite
 -   `addLabel(name, value)` - adds a label to current test
 -   `addParameter(kind, name, value)` - adds a parameter to current test
+-   `createStep(name, stepFunc)` - create a step, stepFunc could consist an attachment
+    Example of usage:
+
+```js
+    allure.createStep('New created step', () => {
+      allure.addAttachment(
+        'Request params',
+        '{"clientId":123, "name":"Tom", "age":29}',
+        'application/json'
+      );
+    });
+```
+
+![Created Step Image][3]
+
 -   `severity(value)` - adds severity label
 -   `epic(value)` - adds epic label
 -   `feature(value)` - adds feature label
@@ -434,7 +449,7 @@ Possible config options:
 
 ## customLocator
 
-Creates a [custom locator][3] by using special attributes in HTML.
+Creates a [custom locator][4] by using special attributes in HTML.
 
 If you have a convention to use `data-test-id` or `data-qa` attributes to mark active elements for e2e tests,
 you can enable this plugin to simplify matching elements with these attributes:
@@ -501,11 +516,76 @@ I.click('=sign-up'); // matches => [data-qa=sign-up]
 
 -   `config`  
 
+## eachElement
+
+Provides `eachElement` global function to iterate over found elements to perform actions on them.
+
+`eachElement` takes following args:
+
+-   `purpose` - the goal of an action. A comment text that will be displayed in output.
+-   `locator` - a CSS/XPath locator to match elements
+-   `fn(element, index)` - **asynchronous** function which will be executed for each matched element.
+
+Example of usage:
+
+```js
+// this example works with Playwright and Puppeteer helper
+await eachElement('click all checkboxes', 'form input[type=checkbox]', async (el) => {
+  await el.click();
+});
+```
+
+Click odd elements:
+
+```js
+// this example works with Playwright and Puppeteer helper
+await eachElement('click odd buttons', '.button-select', async (el, index) => {
+  if (index % 2) await el.click();
+});
+```
+
+Check all elements for visibility:
+
+```js
+// this example works with Playwright and Puppeteer helper
+const assert = require('assert');
+await eachElement('check all items are visible', '.item', async (el) => {
+  assert(await el.isVisible());
+});
+```
+
+This method works with WebDriver, Playwright, Puppeteer, Appium helpers.
+
+Function parameter `el` represents a matched element.
+Depending on a helper API of `el` can be different. Refer to API of corresponding browser testing engine for a complete API list:
+
+-   [Playwright ElementHandle][5]
+-   [Puppeteer][6]
+-   [webdriverio element][7]
+
+#### Configuration
+
+-   `registerGlobal` - to register `eachElement` function globally, true by default
+
+If `registerGlobal` is false you can use eachElement from the plugin:
+
+```js
+const eachElement = codeceptjs.container.plugins('eachElement');
+```
+
+### Parameters
+
+-   `purpose` **[string][8]** 
+-   `locator` **CodeceptJS.LocatorOrString** 
+-   `fn` **[Function][9]** 
+
+Returns **([Promise][10]<any> | [undefined][11])** 
+
 ## fakerTransform
 
-Use the [faker.js][4] package to generate fake data inside examples on your gherkin tests
+Use the [faker.js][12] package to generate fake data inside examples on your gherkin tests
 
-![Faker.js][5]
+![Faker.js][13]
 
 #### Usage
 
@@ -543,7 +623,7 @@ Scenario Outline: ...
 
 ## pauseOnFail
 
-Automatically launches [interactive pause][6] when a test fails.
+Automatically launches [interactive pause][14] when a test fails.
 
 Useful for debugging flaky tests on local environment.
 Add this plugin to config file:
@@ -726,14 +806,14 @@ Possible config options:
 
 ## selenoid
 
-[Selenoid][7] plugin automatically starts browsers and video recording.
+[Selenoid][15] plugin automatically starts browsers and video recording.
 Works with WebDriver helper.
 
 ### Prerequisite
 
 This plugin **requires Docker** to be installed.
 
-> If you have issues starting Selenoid with this plugin consider using the official [Configuration Manager][8] tool from Selenoid
+> If you have issues starting Selenoid with this plugin consider using the official [Configuration Manager][16] tool from Selenoid
 
 ### Usage
 
@@ -762,7 +842,7 @@ plugins: {
   }
 ```
 
-When `autoCreate` is enabled it will pull the [latest Selenoid from DockerHub][9] and start Selenoid automatically.
+When `autoCreate` is enabled it will pull the [latest Selenoid from DockerHub][17] and start Selenoid automatically.
 It will also create `browsers.json` file required by Selenoid.
 
 In automatic mode the latest version of browser will be used for tests. It is recommended to specify exact version of each browser inside `browsers.json` file.
@@ -774,10 +854,10 @@ In automatic mode the latest version of browser will be used for tests. It is re
 While this plugin can create containers for you for better control it is recommended to create and launch containers manually.
 This is especially useful for Continous Integration server as you can configure scaling for Selenoid containers.
 
-> Use [Selenoid Configuration Manager][8] to create and start containers semi-automatically.
+> Use [Selenoid Configuration Manager][16] to create and start containers semi-automatically.
 
 1.  Create `browsers.json` file in the same directory `codecept.conf.js` is located
-    [Refer to Selenoid documentation][10] to know more about browsers.json.
+    [Refer to Selenoid documentation][18] to know more about browsers.json.
 
 _Sample browsers.json_
 
@@ -802,7 +882,7 @@ _Sample browsers.json_
 
 2.  Create Selenoid container
 
-Run the following command to create a container. To know more [refer here][11]
+Run the following command to create a container. To know more [refer here][19]
 
 ```bash
 docker create                                    \
@@ -835,7 +915,7 @@ When `allure` plugin is enabled a video is attached to report automatically.
 | enableVideo      | Enable video recording and use `video` folder of output (default: false)       |
 | enableLog        | Enable log recording and use `logs` folder of output (default: false)          |
 | deletePassed     | Delete video and logs of passed tests (default : true)                         |
-| additionalParams | example: `additionalParams: '--env TEST=test'` [Refer here][12] to know more   |
+| additionalParams | example: `additionalParams: '--env TEST=test'` [Refer here][20] to know more   |
 
 ### Parameters
 
@@ -843,7 +923,7 @@ When `allure` plugin is enabled a video is attached to report automatically.
 
 ## stepByStepReport
 
-![step-by-step-report][13]
+![step-by-step-report][21]
 
 Generates step by step report for a test.
 After each step in a test a screenshot is created. After test executed screenshots are combined into slideshow.
@@ -1024,7 +1104,7 @@ This plugin allows to run webdriverio services like:
 -   browserstack
 -   appium
 
-A complete list of all available services can be found on [webdriverio website][14].
+A complete list of all available services can be found on [webdriverio website][22].
 
 #### Setup
 
@@ -1036,7 +1116,7 @@ See examples below:
 
 #### Selenium Standalone Service
 
-Install `@wdio/selenium-standalone-service` package, as [described here][15].
+Install `@wdio/selenium-standalone-service` package, as [described here][23].
 It is important to make sure it is compatible with current webdriverio version.
 
 Enable `wdio` plugin in plugins list and add `selenium-standalone` service:
@@ -1055,7 +1135,7 @@ Please note, this service can be used with Protractor helper as well!
 
 #### Sauce Service
 
-Install `@wdio/sauce-service` package, as [described here][16].
+Install `@wdio/sauce-service` package, as [described here][24].
 It is important to make sure it is compatible with current webdriverio version.
 
 Enable `wdio` plugin in plugins list and add `sauce` service:
@@ -1089,30 +1169,46 @@ In the same manner additional services from webdriverio can be installed, enable
 
 [2]: https://github.com/allure-framework/allure2/blob/master/plugins/screen-diff-plugin/README.md
 
-[3]: https://codecept.io/locators#custom-locators
+[3]: https://user-images.githubusercontent.com/63167966/139339384-e6e70a62-3638-406d-a224-f32473071428.png
+
+[4]: https://codecept.io/locators#custom-locators
+
+[5]: https://playwright.dev/docs/api/class-elementhandle
+
+[6]: https://pptr.dev/#?product=Puppeteer&show=api-class-elementhandle
+
+[7]: https://webdriver.io/docs/api
+
+[8]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String
+
+[9]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Statements/function
+
+[10]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise
+
+[11]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/undefined
 
-[4]: https://www.npmjs.com/package/faker
+[12]: https://www.npmjs.com/package/faker
 
-[5]: https://raw.githubusercontent.com/Marak/faker.js/master/logo.png
+[13]: https://raw.githubusercontent.com/Marak/faker.js/master/logo.png
 
-[6]: /basics/#pause
+[14]: /basics/#pause
 
-[7]: https://aerokube.com/selenoid/
+[15]: https://aerokube.com/selenoid/
 
-[8]: https://aerokube.com/cm/latest/
+[16]: https://aerokube.com/cm/latest/
 
-[9]: https://hub.docker.com/u/selenoid
+[17]: https://hub.docker.com/u/selenoid
 
-[10]: https://aerokube.com/selenoid/latest/#_prepare_configuration
+[18]: https://aerokube.com/selenoid/latest/#_prepare_configuration
 
-[11]: https://aerokube.com/selenoid/latest/#_option_2_start_selenoid_container
+[19]: https://aerokube.com/selenoid/latest/#_option_2_start_selenoid_container
 
-[12]: https://docs.docker.com/engine/reference/commandline/create/
+[20]: https://docs.docker.com/engine/reference/commandline/create/
 
-[13]: https://codecept.io/img/codeceptjs-slideshow.gif
+[21]: https://codecept.io/img/codeceptjs-slideshow.gif
 
-[14]: https://webdriver.io
+[22]: https://webdriver.io
 
-[15]: https://webdriver.io/docs/selenium-standalone-service.html
+[23]: https://webdriver.io/docs/selenium-standalone-service.html
 
-[16]: https://webdriver.io/docs/sauce-service.html
+[24]: https://webdriver.io/docs/sauce-service.html

package/docs/puppeteer.md

@@ -110,7 +110,6 @@ Tests consist with a scenario of user's action taken on a page. The most widely
 All actions which interact with elements **support CSS and XPath locators**. Actions like `click` or `fillField` by locate elements by their name or value on a page:
 
 ```js
-
 // search for link or button
 I.click('Login');
 // locate field by its label
@@ -172,8 +171,10 @@ If you need to get element's value inside a test you can use `grab*` methods. Th
 ```js
 const assert = require('assert');
 Scenario('get value of current tasks', async ({ I }) => {
-  I.createTodo('do 1');
-  I.createTodo('do 2');
+  I.fillField('.todo', 'my first item');
+  I.pressKey('Enter')
+  I.fillField('.todo', 'my second item');
+  I.pressKey('Enter')
   let numTodos = await I.grabTextFrom('.todo-count strong');
   assert.equal(2, numTodos);
 });
@@ -185,20 +186,35 @@ In case some actions should be taken inside one element (a container or modal wi
 Please take a note that you can't use within inside another within in Puppeteer helper:
 
 ```js
-within('.todoapp', () => {
-  I.createTodo('my new item');
+await within('.todoapp', () => {
+  I.fillField('.todo', 'my new item');
+  I.pressKey('Enter')
   I.see('1 item left', '.todo-count');
   I.click('.todo-list input.toggle');
 });
 I.see('0 items left', '.todo-count');
 ```
 
-> [▶ Learn more about basic commands](/basics#writing-tests)
+### Each Element <Badge text="Since 3.3" type="warning"/>
+
+Usually, CodeceptJS performs an action on the first matched element. 
+In case you want to do an action on each element found, use the special function `eachElement` which comes from [eachElement](https://codecept.io/plugins/#eachelement) plugin. 
+
+`eachElement` function matches all elements by locator and performs a callback on each of those element. A callback function receives [ElementHandle instance](https://pptr.dev/#?product=Puppeteer&show=api-class-elementhandle) from Puppeteer API. `eachElement` may perform arbitrary actions on a page, so the first argument should by a description of the actions performed. This description will be used for logging purposes.
 
-CodeceptJS allows you to implement custom actions like `I.createTodo` or use **PageObjects**. Learn how to improve your tests in [PageObjects](https://codecept.io/pageobjects/) guide.
+Usage example
 
-> [▶ Demo project is available on GitHub](https://github.com/DavertMik/codeceptjs-todomvc-puppeteer)
+```js
+await eachElement(
+  'click all checkboxes', 
+  'input.custom-checkbox', 
+  async (el, index) => {
+    await el.click();
+  });
+);
+```
 
+> ℹ Learn more about [eachElement plugin](/plugins/#eachelement)
 
 ## Mocking Requests
 

package/docs/quickstart.md

@@ -37,9 +37,6 @@ TestCafe provides cross-browser support without Selenium. TestCafe tests are fas
 
 # Quickstart
 
-> CodeceptJS supports various engines for running browser tests. By default we recommend using **Playwright** which is cross-browser and performant solution.
-
-
 
 Use [CodeceptJS all-in-one installer](https://github.com/codeceptjs/create-codeceptjs) to get CodeceptJS, a demo project, and Playwright.
 
@@ -47,6 +44,8 @@ Use [CodeceptJS all-in-one installer](https://github.com/codeceptjs/create-codec
 npx create-codeceptjs .
 ```
 
+If you prefer not to use Playwright see other [installation options](/installation/).
+
 ![Installation](/img/codeceptinstall.gif)
 
 > To install codeceptjs into a different folder, like `tests` use `npx create-codeceptjs tests`

package/docs/reports.md

@@ -141,9 +141,50 @@ npx codecepjs dry-run --debug
 
 > ℹ If you use custom JavaScript code inside tests, or rely on values from `grab*` commands, dry-run may produce error output.
 
+
+## Testomat.io
+
+[Testomat.io](https://testomat.io) is a modern test management tool focused on CodeceptJS and **created by CodeceptJS team**.
+Testomat.io is commercial SaaS service that can receive run reports from local runs or CI. Out of box Testomat.io supports parallel runs, uploading of screenshots and videos.
+
+![](https://user-images.githubusercontent.com/220264/151728836-b52d2b2b-56e1-4640-8d3a-b39de817b1fd.png)
+
+> 😻 **Testomat.io is free** for small teams, so you can use its reporting features with CodeceptJS.
+
+To receive run reports you should:
+
+* [Sign up](https://app.testomat.io/users/sign_up) at Testomat.io
+* Create a new "Classical" project (select "BDD" project if you use CodeceptJS in BDD mode)
+* Select "Import from Source Code"
+* Select "CodeceptJS" as testing framework and JavaScript or TypeScript as a language. If you use BDD select "Gherkin" as language.
+* Execute provided command in a terminal with your project. This will be "check-tests" or "check-cucmber" command. It scans all your test files and imports them into Testomat.io. This way all your e2e tests will be visible in one UI.
+* After tests are imported, go to Runs tab and select "Setup automated tests".
+* Follow the instructions:
+
+
+![image](https://user-images.githubusercontent.com/77803888/151834217-5da44d92-a59a-458d-8856-64ce61bf3a38.png)
+
+* You will need to install `@testomatio/reporter` package and enable it as a plugin in codeceptjs config:
+
+```js
+plugins: {
+  testomatio: {
+    enabled: true,
+    require: '@testomatio/reporter/lib/adapter/codecept',
+    apiKey: process.env.TESTOMATIO,
+  }
+}
+```
+
+* Run tests with `TESTOMATIO=` env variable and API key provided by Testomat.io
+* See the run report is created and updated in realtime.
+
+
+[Testomat.io](https://testomat.io) reporter works in the cloud, so it doesn't require you to install additional software. It can be integrated with your CI service to rerun only failed tests, launch new runs from UI, and send report notifications by email or in Slack, MS Teams, or create issue in Jira.
+
+
 ## Allure
 
-> ℹ  We recommend using Allure reports on CI. Allure is one of the best open-source reporters designed to collect and show test reports in nicest way.
 
 [Allure reporter](https://allure.qatools.ru/#) is a tool to store and display test reports.
 It provides nice web UI which contains all important information on test execution.
@@ -201,7 +242,7 @@ npx codeceptjs dry-run --debug -p allure
 
 ## ReportPortal
 
-Allure is a great reporting tool, however, if you are running tests on different machines it is hard to merge its XML result files to build a proper report. So, for enterprise grade reporting we recommend using [ReportPortal](https://reportportal.io).
+For enterprise grade we reporting we recommend using [ReportPortal](https://reportportal.io).
 
 ![](https://camo.githubusercontent.com/6550c0365f1d0ce1e29c53f1860b12957d1fc529/68747470733a2f2f692e6962622e636f2f516d353247306e2f53637265656e73686f742d323031392d30342d31312d61742d31352d35372d34302e706e67)
 

package/docs/translation.md

@@ -57,7 +57,7 @@ To write your tests in portuguese you can enable the portuguese translation in c
 Now you can write test like this:
 
 ```js
-Scenario('Efetuar login', ({ Eu }) => {
+Cenário('Efetuar login', ({ Eu }) => {
     Eu.estouNaPagina('http://minhaAplicacao.com.br');
     Eu.preenchoOCampo("login", "usuario@minhaAplicacao.com.br");
     Eu.preenchoOCampo("senha", "123456");

package/docs/videos.md

@@ -7,7 +7,7 @@ editLink: false
 ---
 
 > Add your own videos to our [Wiki Page](https://github.com/codeceptjs/CodeceptJS/wiki/Videos)
-[![](http://i3.ytimg.com/vi/BRMWstiOTks/maxresdefault.jpg)](https://www.youtube.com/watch?v=BRMWstiOTks)
+[![](https://i3.ytimg.com/vi/BRMWstiOTks/maxresdefault.jpg)](https://www.youtube.com/watch?v=BRMWstiOTks)
 
 ## [An Introduction, Getting started and working with CodeceptJS & Puppeteer (EAWeekend)](https://www.youtube.com/watch?v=BRMWstiOTks)
 
@@ -15,7 +15,7 @@ editLink: false
 
 ## [Introductory Videos](https://www.youtube.com/watch?v=FPFG1rBNJ64&list=PLcFXthgti9Lt4SjSvL1ALDg6dOeTC0TvT)
 
-Free educational videos provided by our community member **[@ontytoom](http://github.com/ontytoom)**.
+Free educational videos provided by our community member **[@ontytoom](https://github.com/ontytoom)**.
 
 1. [Installation](https://www.youtube.com/watch?v=FPFG1rBNJ64)
 1. [Creating a Test](https://www.youtube.com/watch?v=mdQZjL3h9d0)

package/docs/webdriver.md

@@ -203,8 +203,6 @@ Scenario('login test', ({ I }) => {
   I.see('Welcome, John');
 });
 ```
-> ▶ Actions like `amOnPage`, `click`, `fillField` are not limited to WebDriver only. They work similarly for all available helpers. [Go to Basics guide to learn them](/basics#writing-tests).
-
 
 An empty test case can be created with `npx codeceptjs gt` command.
 
@@ -212,6 +210,43 @@ An empty test case can be created with `npx codeceptjs gt` command.
 npx codeceptjs gt
 ```
 
+
+### Actions
+
+Tests consist with a scenario of user's action taken on a page. The most widely used ones are:
+
+* `amOnPage` - to open a webpage (accepts relative or absolute url)
+* `click` - to locate a button or link and click on it
+* `fillField` - to enter a text inside a field
+* `selectOption`, `checkOption` - to interact with a form
+* `wait*` to wait for some parts of page to be fully rendered (important for testing SPA)
+* `grab*` to get values from page sources
+* `see`, `dontSee` - to check for a text on a page
+* `seeElement`, `dontSeeElement` - to check for elements on a page
+
+> ℹ  All actions are listed in [WebDriver helper reference](https://codecept.io/helpers/WebDriver/).*
+
+All actions which interact with elements **support CSS and XPath locators**. Actions like `click` or `fillField` by locate elements by their name or value on a page:
+
+```js
+// search for link or button
+I.click('Login');
+// locate field by its label
+I.fillField('Name', 'Miles');
+// we can use input name
+I.fillField('user[email]','miles@davis.com');
+```
+
+You can also specify the exact locator type with strict locators:
+
+```js
+I.click({css: 'button.red'});
+I.fillField({name: 'user[email]'},'miles@davis.com');
+I.seeElement({xpath: '//body/header'});
+```
+
+### Interactive Pause
+
 It's easy to start writing a test if you use [interactive pause](/basics#debug). Just open a web page and pause execution.
 
 ```js
@@ -268,6 +303,59 @@ Scenario('create todo item', ({ I }) => {
 
 WebDriver helper supports standard [CSS/XPath and text locators](/locators) as well as non-trivial [React locators](/react) and [Shadow DOM](/shadow).
 
+### Grabbers
+
+If you need to get element's value inside a test you can use `grab*` methods. They should be used with `await` operator inside `async` function:
+
+```js
+const assert = require('assert');
+Scenario('get value of current tasks', async ({ I }) => {
+  I.fillField('.todo', 'my first item');
+  I.pressKey('Enter')
+  I.fillField('.todo', 'my second item');
+  I.pressKey('Enter')
+  let numTodos = await I.grabTextFrom('.todo-count strong');
+  assert.equal(2, numTodos);
+});
+```
+
+### Within
+
+In case some actions should be taken inside one element (a container or modal window or iframe) you can use `within` block to narrow the scope.
+Please take a note that you can't use within inside another within in Puppeteer helper:
+
+```js
+await within('.todoapp', () => {
+  I.fillField('.todo', 'my new item');
+  I.pressKey('Enter')
+  I.see('1 item left', '.todo-count');
+  I.click('.todo-list input.toggle');
+});
+I.see('0 items left', '.todo-count');
+```
+
+### Each Element <Badge text="Since 3.3" type="warning"/>
+
+Usually, CodeceptJS performs an action on the first matched element. 
+In case you want to do an action on each element found, use the special function `eachElement` which comes from [eachElement](https://codecept.io/plugins/#eachelement) plugin. 
+
+`eachElement` function matches all elements by locator and performs a callback on each of those element. A callback function receives element of webdriverio. `eachElement` may perform arbitrary actions on a page, so the first argument should by a description of the actions performed. This description will be used for logging purposes.
+
+Usage example
+
+```js
+await eachElement(
+  'click all checkboxes', 
+  'input.custom-checkbox', 
+  async (el, index) => {
+    await el.click();
+  });
+);
+```
+
+> ℹ Learn more about [eachElement plugin](/plugins/#eachelement)
+
+
 ## Waiting
 
 Web applications do not always respond instantly. That's why WebDriver protocol has methods to wait for changes on a page. CodeceptJS provides such commands prefixed with `wait*` so you could explicitly define what effects we wait for.

package/lib/command/init.js

@@ -22,7 +22,7 @@ const defaultConfig = {
   mocha: {},
 };
 
-const helpers = ['Playwright', 'WebDriver', 'Puppeteer', 'TestCafe', 'Protractor', 'Nightmare', 'Appium'];
+const helpers = ['Playwright', 'WebDriver', 'Puppeteer', 'REST', 'GraphQL', 'Appium', 'TestCafe', 'Nightmare'];
 const translations = Object.keys(require('../../translations'));
 
 const noTranslation = 'English (no localization)';
@@ -30,12 +30,15 @@ translations.unshift(noTranslation);
 
 let packages;
 
-const configHeader = `const { setHeadlessWhen } = require('@codeceptjs/configure');
+const configHeader = `const { setHeadlessWhen, setCommonPlugins } = require('@codeceptjs/configure');
 
 // turn on headless mode when running with HEADLESS=true environment variable
 // export HEADLESS=true && npx codeceptjs run
 setHeadlessWhen(process.env.HEADLESS);
 
+// enable all common plugins https://github.com/codeceptjs/configure#setcommonplugins
+setCommonPlugins();
+
 `;
 
 const defaultActor = `// in this file you can append custom step methods to 'I' object
@@ -150,19 +153,6 @@ module.exports = function (initPath) {
       config.include.I = stepFile;
       print(`Steps file created at ${stepFile}`);
 
-      config.plugins = {
-        pauseOnFail: {},
-        retryFailedStep: {
-          enabled: true,
-        },
-        tryTo: {
-          enabled: true,
-        },
-        screenshotOnFail: {
-          enabled: true,
-        },
-      };
-
       let configSource = beautify(`exports.config = ${inspect(config, false, 4, false)}`);
 
       if (require.resolve('@codeceptjs/configure') && isLocal && !initPath) {

package/lib/config.js

@@ -38,6 +38,14 @@ const defaultConfig = {
 let hooks = [];
 let config = {};
 
+const configFileNames = [
+  'codecept.config.js',
+  'codecept.conf.js',
+  'codecept.json',
+  'codecept.config.ts',
+  'codecept.conf.ts',
+];
+
 /**
  * Current configuration
  */
@@ -59,6 +67,7 @@ class Config {
    * If js file provided: require it and get .config key
    * If json file provided: load and parse JSON
    * If directory provided:
+   * * try to load `codecept.config.js` from it
    * * try to load `codecept.conf.js` from it
    * * try to load `codecept.json` from it
    * If none of above: fail.
@@ -78,23 +87,18 @@ class Config {
       return loadConfigFile(configFile);
     }
 
-    // is path to directory
-    const jsConfig = path.join(configFile, 'codecept.conf.js');
-    if (isFile(jsConfig)) {
-      return loadConfigFile(jsConfig);
-    }
+    for (const name of configFileNames) {
+      // is path to directory
+      const jsConfig = path.join(configFile, name);
 
-    const jsonConfig = path.join(configFile, 'codecept.json');
-    if (isFile(jsonConfig)) {
-      return loadConfigFile(jsonConfig);
+      if (isFile(jsConfig)) {
+        return loadConfigFile(jsConfig);
+      }
     }
 
-    const tsConfig = path.join(configFile, 'codecept.conf.ts');
-    if (isFile(tsConfig)) {
-      return loadConfigFile(tsConfig);
-    }
+    const configPaths = configFileNames.map(name => path.join(configFile, name)).join(' or ');
 
-    throw new Error(`Can not load config from ${jsConfig} or ${jsonConfig} or ${tsConfig}\nCodeceptJS is not initialized in this dir. Execute 'codeceptjs init' to start`);
+    throw new Error(`Can not load config from ${configPaths}\nCodeceptJS is not initialized in this dir. Execute 'codeceptjs init' to start`);
   }
 
   /**