codeceptjs 3.2.2 → 3.2.3

package/docs/installation.md

@@ -57,7 +57,7 @@ For WebDriver installation Selenium Server is required 👇
 
 ## WebDriver
 
-WebDriver based helpers like WebDriver, Protractor, Selenium WebDriver will require [Selenium Server](http://codecept.io/helpers/WebDriver/#selenium-installation) installed. They will also require ChromeDriver or GeckoDriver to run corresponding browsers.
+WebDriver based helpers like WebDriver, Protractor, Selenium WebDriver will require [Selenium Server](https://codecept.io/helpers/WebDriver/#selenium-installation) installed. They will also require ChromeDriver or GeckoDriver to run corresponding browsers.
 
 We recommend to install them manually or use NPM packages:
 

package/docs/mobile.md

@@ -6,7 +6,7 @@ title: Mobile Testing with Appium
 # Mobile Testing with Appium
 
 CodeceptJS allows to test mobile and hybrid apps in a similar manner web applications are tested.
-Such tests are executed using [Appium](http://appium.io) on emulated or physical devices. Also, Appium allows to test web application on mobile devices.
+Such tests are executed using [Appium](https://appium.io) on emulated or physical devices. Also, Appium allows to test web application on mobile devices.
 
 What makes CodeceptJS better for mobile testing?
 Take a look. Here is the sample test for a native mobile application written in CodeceptJS:
@@ -14,10 +14,10 @@ Take a look. Here is the sample test for a native mobile application written in
 ```js
 I.seeAppIsInstalled("io.super.app");
 I.click('~startUserRegistrationCD');
-I.fillField('~email of the customer', 'Nothing special'));
-I.see('davert@codecept.io', '~email of the customer'));
-I.clearField('~email of the customer'));
-I.dontSee('Nothing special', '~email of the customer'));
+I.fillField('~email of the customer', 'Nothing special');
+I.see('davert@codecept.io', '~email of the customer');
+I.clearField('~email of the customer');
+I.dontSee('Nothing special', '~email of the customer');
 I.seeElement({
   android: 'android.widget.Button',
   ios: '//UIAApplication[1]/UIAWindow[1]/UIAButton[1]'
@@ -29,15 +29,15 @@ Doesn't it sound cool?
 
 ## Setting Up
 
-Ensure that you have [CodeceptJS installed](http://codecept.io/installation/).
-You will also need to install [Appium](http://appium.io/).
+Ensure that you have [CodeceptJS installed](https://codecept.io/installation/).
+You will also need to install [Appium](https://appium.io/).
 We suggest to use [appium-doctor](https://www.npmjs.com/package/appium-doctor) to check if your system is ready for mobile testing.
 
 ```sh
 npm i -g appium-doctor
 ```
 
-If everything is OK, continue with installing Appium. If not, consider using cloud based alternatives like [SauceLabs](https://saucelabs.com) or [BrowserStack](http://browserstack.com). Cloud services provide hosted appium with real and emulated mobile devices.
+If everything is OK, continue with installing Appium. If not, consider using cloud based alternatives like [SauceLabs](https://saucelabs.com) or [BrowserStack](https://browserstack.com). Cloud services provide hosted appium with real and emulated mobile devices.
 
 To install Appium use npm:
 
@@ -71,7 +71,7 @@ Initialize CodeceptJS with `init` command:
 npx codeceptjs init
 ```
 
-Select [Appium helper](http://codecept.io/helpers/Appium/) when asked.
+Select [Appium helper](https://codecept.io/helpers/Appium/) when asked.
 
 ```sh
 ? What helpers do you want to use?
@@ -166,7 +166,7 @@ There are mobile-only methods like:
 * `hideDeviceKeyboard`,
 * `seeAppIsInstalled`, `installApp`, `removeApp`, `seeAppIsNotInstalled` - Android only
 
-and [others](http://codecept.io/helpers/Appium/).
+and [others](https://codecept.io/helpers/Appium/).
 
 ## Locating Elements
 
@@ -211,7 +211,7 @@ I.tap('Click me!');
 I.click('Click me!');
 ```
 
-Native iOS/Android locators can be used with `android=` and `ios=` prefixes. [Learn more](http://webdriver.io/guide/usage/selectors.html#Mobile-Selectors).
+Native iOS/Android locators can be used with `android=` and `ios=` prefixes. [Learn more](https://webdriver.io/guide/usage/selectors.html#Mobile-Selectors).
 
 But how to get all those locators? We recommend to use [Appium Inspector](https://github.com/appium/appium-desktop).
 

package/docs/nightmare.md

@@ -11,7 +11,7 @@ This hardens setting it up testing environment for CI server and slows down test
 
 Is there a sane alternative to Selenium?
 
-Yes, how about [NightmareJS](http://www.nightmarejs.org)?
+Yes, how about [NightmareJS](https://www.nightmarejs.org)?
 
 It is modern Electron based testing framework which allows to execute tests in headless mode as well as in window mode for debug purposes.
 This makes Nightmare very useful, much more handy than PhantomJS. Nightmare is in active development and has nice API for writing acceptance tests.
@@ -105,7 +105,7 @@ codeceptjs init
 ```
 
 You will be asked for a Helper to use, you should select Nightmare and provide url of a website you are testing.
-Setup process is explained on [QuickStart page](http://codecept.io/quickstart/).
+Setup process is explained on [QuickStart page](https://codecept.io/quickstart/).
 
 (If you already have CodeceptJS project, just install nightmare globally or locally and enable it in config)
 
@@ -171,7 +171,7 @@ Nightmare helper is missing you can easily create `ExtendedNightmare` helper by
 codeceptjs gh
 ```
 
-Learn more about [Helpers](http://codecept.io/helpers/).
+Learn more about [Helpers](https://codecept.io/helpers/).
 
 Nightmare instance can be accessed by custom helper:
 

package/docs/playwright.md

@@ -31,7 +31,7 @@ To start you need CodeceptJS with Playwright packages installed
 npm install codeceptjs playwright --save
 ```
 
-Or see [alternative installation options](http://codecept.io/installation/)
+Or see [alternative installation options](https://codecept.io/installation/)
 
 > If you already have CodeceptJS project, just install `playwright` package and enable a helper it in config.
 
@@ -84,7 +84,7 @@ When to consider navigation succeeded, defaults to `load`. Given an array of eve
 When a test runs faster than application it is recommended to increase `waitForAction` config value.
 It will wait for a small amount of time (100ms) by default after each user action is taken.
 
-> ▶ More options are listed in [helper reference](http://codecept.io/helpers/Playwright/).
+> ▶ More options are listed in [helper reference](https://codecept.io/helpers/Playwright/).
 
 ## Writing Tests
 
@@ -109,7 +109,7 @@ Tests consist with a scenario of user's action taken on a page. The most widely
 * `see`, `dontSee` - to check for a text on a page
 * `seeElement`, `dontSeeElement` - to check for elements on a page
 
-> ℹ  All actions are listed in [Playwright helper reference](http://codecept.io/helpers/Playwright/).*
+> ℹ  All actions are listed in [Playwright helper reference](https://codecept.io/helpers/Playwright/).*
 
 All actions which interact with elements can use **[CSS or XPath locators](https://codecept.io/locators/#css-and-xpath)**. Actions like `click` or `fillField` can locate elements by their name or value on a page:
 
@@ -198,7 +198,7 @@ I.see('0 items left', '.todo-count');
 
 > [▶ Learn more about basic commands](/basics#writing-tests)
 
-CodeceptJS allows you to implement custom actions like `I.createTodo` or use **PageObjects**. Learn how to improve your tests in [PageObjects](http://codecept.io/pageobjects/) guide.
+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.
 
 ## Multi Session Testing
 

package/docs/plugins.md

@@ -127,7 +127,7 @@ If a session expires automatically logs in again.
 ```js
 // inside a test file
 // use login to inject auto-login function
-Before(login => {
+Before(({ login }) => {
    login('user'); // login using user session
 });
 
@@ -981,18 +981,22 @@ Use this plugin if:
 
 #### Multiple Conditional Assertions
 
+````js
+Add assert requires first:
 ```js
+const assert = require('assert');
+````
+
+Then use the assert:
 const result1 = await tryTo(() => I.see('Hello, user'));
 const result2 = await tryTo(() => I.seeElement('.welcome'));
 assert.ok(result1 && result2, 'Assertions were not succesful');
-```
 
-##### Optional click
+    ##### Optional click
 
-```js
-I.amOnPage('/');
-tryTo(() => I.click('Agree', '.cookies'));
-```
+    ```js
+    I.amOnPage('/');
+    tryTo(() => I.click('Agree', '.cookies'));
 
 #### Configuration
 

package/docs/puppeteer.md

@@ -31,7 +31,7 @@ To start you need CodeceptJS with Puppeteer packages installed
 npm install codeceptjs puppeteer --save
 ```
 
-Or see [alternative installation options](http://codecept.io/installation/)
+Or see [alternative installation options](https://codecept.io/installation/)
 
 > If you already have CodeceptJS project, just install `puppeteer` package and enable a helper it in config.
 
@@ -80,7 +80,7 @@ By default it is set to `domcontentloaded` which waits for `DOMContentLoaded` ev
 When a test runs faster than application it is recommended to increase `waitForAction` config value.
 It will wait for a small amount of time (100ms) by default after each user action is taken.
 
-> ▶ More options are listed in [helper reference](http://codecept.io/helpers/Puppeteer/).
+> ▶ More options are listed in [helper reference](https://codecept.io/helpers/Puppeteer/).
 
 ## Writing Tests
 
@@ -105,7 +105,7 @@ Tests consist with a scenario of user's action taken on a page. The most widely
 * `see`, `dontSee` - to check for a text on a page
 * `seeElement`, `dontSeeElement` - to check for elements on a page
 
-> ℹ  All actions are listed in [Puppeteer helper reference](http://codecept.io/helpers/Puppeteer/).*
+> ℹ  All actions are listed in [Puppeteer helper reference](https://codecept.io/helpers/Puppeteer/).*
 
 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:
 
@@ -195,7 +195,7 @@ I.see('0 items left', '.todo-count');
 
 > [▶ Learn more about basic commands](/basics#writing-tests)
 
-CodeceptJS allows you to implement custom actions like `I.createTodo` or use **PageObjects**. Learn how to improve your tests in [PageObjects](http://codecept.io/pageobjects/) guide.
+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.
 
 > [▶ Demo project is available on GitHub](https://github.com/DavertMik/codeceptjs-todomvc-puppeteer)
 
@@ -297,4 +297,4 @@ async renderPageToPdf() {
 
 The same way you can also access `browser` object to implement more actions or handle events.
 
-> [▶ Learn more about Helpers](http://codecept.io/helpers/)
+> [▶ Learn more about Helpers](https://codecept.io/helpers/)

package/docs/reports.md

@@ -145,7 +145,7 @@ npx codecepjs dry-run --debug
 
 > ℹ  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](http://allure.qatools.ru/#) is a tool to store and display test reports.
+[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.
 CodeceptJS has built-in support for Allure reports. Inside reports you will have all steps, substeps and screenshots.
 

package/docs/testcafe.md

@@ -54,7 +54,7 @@ A first test should be created with `codeceptjs gt` command
 npx codeceptjs gt
 ```
 
-In the next example we will [TodoMVC application](http://todomvc.com/examples/angularjs/#/). So let's create a test which will fill in todo list:
+In the next example we will [TodoMVC application](https://todomvc.com/examples/angularjs/#/). So let's create a test which will fill in todo list:
 
 ```js
 Feature('TodoMVC');

package/docs/translation.md

@@ -38,7 +38,7 @@ This way tests can be written in native language while it is still JavaScript:
 
 ```js
 Сценарий('пробую написать реферат', (Я) => {
-    Я.на_странице('http://yandex.ru/referats');
+    Я.на_странице('https://yandex.ru/referats');
     Я.вижу("Написать реферат по");
     Я.выбираю_опцию('Психологии');
     Я.кликаю("Написать реферат");

package/docs/visual.md

@@ -58,7 +58,7 @@ Base Image is compared with the screenshot image and test results are derived ba
 
 ### Example
 
-Lets consider visual testing for [CodeceptJS Home](http://codecept.io)
+Lets consider visual testing for [CodeceptJS Home](https://codecept.io)
 
 ```js
 Feature('To test screen comparison with resemble Js Example test');
@@ -183,7 +183,7 @@ The first time you run this test a new baseline will be created, and subsequent
 
 ### Example
 
-Lets consider visual testing for [CodeceptJS Home](http://codecept.io).
+Lets consider visual testing for [CodeceptJS Home](https://codecept.io).
 You can also find example repo here: https://github.com/PeterNgTr/codeceptjs-applitoolshelper
 
 ```js

package/docs/vue.md

@@ -111,7 +111,7 @@ If you agreed to create a demo component, you will also see `TestMe` component i
 * [Learn CodeceptJS basics](/basics)
 * [Learn how to write CodeceptJS tests with Puppeteer](/puppeteer)
 * [See full reference for CodeceptJS Puppeteer Helper](/helpers/Puppeteer)
-* Ask your questions in [Slack](http://bit.ly/chat-codeceptjs) & [Forum](https://codecept.discourse.group/)
+* Ask your questions in [Slack](https://bit.ly/chat-codeceptjs) & [Forum](https://codecept.discourse.group/)
 
 ## Enjoy testing!
 

package/docs/webdriver.md

@@ -250,7 +250,7 @@ An interactive shell output may look like this:
 ```
 After typing in successful commands you can copy them into a test.
 
-Here is a test checking basic [todo application](http://todomvc.com/).
+Here is a test checking basic [todo application](https://todomvc.com/).
 
 ```js
 Feature('TodoMVC');
@@ -295,7 +295,7 @@ exports.config = {
 
 ## SmartWait
 
-It is possible to wait for elements pragmatically. If a test uses element which is not on a page yet, CodeceptJS will wait for few extra seconds before failing. This feature is based on [Implicit Wait](http://www.seleniumhq.org/docs/04_webdriver_advanced.jsp#implicit-waits) of Selenium. CodeceptJS enables implicit wait only when searching for a specific element and disables in all other cases. Thus, the performance of a test is not affected.
+It is possible to wait for elements pragmatically. If a test uses element which is not on a page yet, CodeceptJS will wait for few extra seconds before failing. This feature is based on [Implicit Wait](https://www.seleniumhq.org/docs/04_webdriver_advanced.jsp#implicit-waits) of Selenium. CodeceptJS enables implicit wait only when searching for a specific element and disables in all other cases. Thus, the performance of a test is not affected.
 
 SmartWait can be enabled by setting wait option in WebDriver config.
 Add `smartWait: 5000` to wait for additional 5s.

package/lib/cli.js

@@ -7,6 +7,7 @@ const { MetaStep } = require('./step');
 
 const cursor = Base.cursor;
 let currentMetaStep = [];
+let codeceptjsEventDispatchersRegistered = false;
 
 class Cli extends Base {
   constructor(runner, opts) {
@@ -77,29 +78,33 @@ class Cli extends Base {
         }
       });
 
-      event.dispatcher.on(event.step.started, (step) => {
-        let processingStep = step;
-        const metaSteps = [];
-        while (processingStep.metaStep) {
-          metaSteps.unshift(processingStep.metaStep);
-          processingStep = processingStep.metaStep;
-        }
-        const shift = metaSteps.length;
+      if (!codeceptjsEventDispatchersRegistered) {
+        codeceptjsEventDispatchersRegistered = true;
 
-        for (let i = 0; i < Math.max(currentMetaStep.length, metaSteps.length); i++) {
-          if (currentMetaStep[i] !== metaSteps[i]) {
-            output.stepShift = 3 + 2 * i;
-            if (metaSteps[i]) output.step(metaSteps[i]);
+        event.dispatcher.on(event.step.started, (step) => {
+          let processingStep = step;
+          const metaSteps = [];
+          while (processingStep.metaStep) {
+            metaSteps.unshift(processingStep.metaStep);
+            processingStep = processingStep.metaStep;
           }
-        }
-        currentMetaStep = metaSteps;
-        output.stepShift = 3 + 2 * shift;
-        output.step(step);
-      });
+          const shift = metaSteps.length;
 
-      event.dispatcher.on(event.step.finished, () => {
-        output.stepShift = 0;
-      });
+          for (let i = 0; i < Math.max(currentMetaStep.length, metaSteps.length); i++) {
+            if (currentMetaStep[i] !== metaSteps[i]) {
+              output.stepShift = 3 + 2 * i;
+              if (metaSteps[i]) output.step(metaSteps[i]);
+            }
+          }
+          currentMetaStep = metaSteps;
+          output.stepShift = 3 + 2 * shift;
+          output.step(step);
+        });
+
+        event.dispatcher.on(event.step.finished, () => {
+          output.stepShift = 0;
+        });
+      }
     }
 
     runner.on('suite end', suite => {

package/lib/command/workers/runTests.js

@@ -73,6 +73,27 @@ function filterTests() {
 }
 
 function initializeListeners() {
+  function simplifyError(error) {
+    if (error) {
+      const {
+        stack,
+        uncaught,
+        message,
+        actual,
+        expected,
+      } = error;
+
+      return {
+        stack,
+        uncaught,
+        message,
+        actual,
+        expected,
+      };
+    }
+
+    return null;
+  }
   function simplifyTest(test, err = null) {
     test = { ...test };
 
@@ -82,13 +103,10 @@ function initializeListeners() {
     }
 
     if (test.err) {
-      err = {
-        stack: test.err.stack,
-        uncaught: test.err.uncaught,
-        message: test.err.message,
-        actual: test.err.actual,
-        expected: test.err.expected,
-      };
+      err = simplifyError(test.err);
+      test.status = 'failed';
+    } else if (err) {
+      err = simplifyError(err);
       test.status = 'failed';
     }
     const parent = {};