codeceptjs 2.3.4 → 2.4.1

package/docs/hooks.md

@@ -1,8 +1,9 @@
 ---
-id: hooks
+permalink: /hooks
 title: Bootstrap / Teardown / Plugins
 ---
 
+# Bootstrap / Teardown / Plugins
 
 CodeceptJS provides API to run custom code before and after the test and inject custom listeners into the event system.
 
@@ -131,7 +132,7 @@ First, `bootstrapAll` is called. Then two `bootstrap` runs in each of workers. T
 
 The `bootstrapAll` and `teardownAll` hooks are preferred to use for setting up common logic of tested project: to start application server or database, to start webdriver's grid.
 
-The `bootstrap` and `teardown` hooks are used for setting up each testing browser: to create unique [cloud testing server](https://codecept.io/helpers/WebDriverIO#cloud-providers) connection or to create specific browser-related test data in database (like users with names with browsername in it).
+The `bootstrap` and `teardown` hooks are used for setting up each testing browser: to create unique [cloud testing server](/helpers/WebDriverIO#cloud-providers) connection or to create specific browser-related test data in database (like users with names with browsername in it).
 
 Same as `bootstrap` and `teardown`, there are 3 ways to define `bootstrapAll` and `teardownAll` functions:
 
@@ -239,7 +240,7 @@ module.exports = {
 
 Plugins allow to use CodeceptJS internal API to extend functionality. Use internal event dispatcher, container, output, promise recorder, to create your own reporters, test listeners, etc.
 
-CodeceptJS includes [built-in plugins](https://codecept.io/plugins/) which extend basic functionality and can be turned on and off on purpose. Taking them as [examples](https://github.com/Codeception/CodeceptJS/tree/master/lib/plugin) you can develop your custom plugins.
+CodeceptJS includes [built-in plugins](/plugins/) which extend basic functionality and can be turned on and off on purpose. Taking them as [examples](https://github.com/Codeception/CodeceptJS/tree/master/lib/plugin) you can develop your custom plugins.
 
 A plugin is a basic JS module returning a function. Plugins can have individual configs which are passed into this function:
 
@@ -284,7 +285,7 @@ Several plugins can be enabled as well:
 
 ### Example: Execute code for a specific group of tests
 
-If you need to execute some code before a group of tests, you can [mark these tests with a same tag](https://codecept.io/advanced/#tags). Then to listen for tests where this tag is included (see [test object api](#test-object)).
+If you need to execute some code before a group of tests, you can [mark these tests with a same tag](/advanced/#tags). Then to listen for tests where this tag is included (see [test object api](#test-object)).
 
 Let's say we need to populate database for a group of tests.
 
@@ -399,7 +400,9 @@ Test events provide a test object with following fields:
 * `tags` array of tags for this test
 * `file` path to a file with a test.
 * `steps` array of executed steps (available only in `test.passed`, `test.failed`, `test.finished` event)
-
+* `skipInfo` additional test options when test skipped 
+* * `message` string with reason for skip
+* * `description` string with test body
 and others
 
 #### Step Object
@@ -530,18 +533,19 @@ if (config.myKey == 'value') {
 
 ## Custom Runner
 
+> 📺 [Watch this](https://www.youtube.com/watch?v=3eZtVL0Ad0A) material on YouTube
+
 CodeceptJS can be imported and used in custom runners.
 To initialize Codecept you need to create Config and Container objects.
 
 ```js
-let Container = require('codeceptjs').container;
-let Codecept = require('codeceptjs').codecept;
+const { container: Container, codecept: Codecept } = require('codeceptjs').container;
 
-let config = { helpers: { WebDriver: { browser: 'chrome', url: 'http://localhost' } } };
-let opts = { steps: true };
+const config = { helpers: { WebDriver: { browser: 'chrome', url: 'http://localhost' } } };
+const opts = { steps: true };
 
 // create runner
-let codecept = new Codecept(config, opts);
+const codecept = new Codecept(config, opts);
 
 // initialize codeceptjs in current dir
 codecept.initGlobals(__dirname);

package/docs/index.md

@@ -0,0 +1,112 @@
+---
+layout: Landing
+sidebar: false
+actionText: Quickstart
+actionLink: /quickstart
+---
+
+::: slot pause
+## Write a Test with Interactive Pause
+
+Open a browser on an empty page and pause execution.
+Type in commands to complete the test scenario.
+
+Successful commands will be saved into a file.
+
+```js
+Scenario('Checkout test', () => {
+  I.amOnPage('/checkout');
+  pause();
+})
+```
+Copy commands from a file into a test. A test is ready!
+:::
+
+::: slot write
+## Write Tests from UI
+
+With CodeceptUI you can write your tests without closing a browser at all.
+
+Write initial commands and execute a test. An interactive pause will be started when test finishes.
+
+Share one browser accross test runs to save time on opening a browser.
+:::
+
+
+::: slot autocomplete
+## Powered with IntelliSense
+
+Use auto-completion writing a test fast.
+
+We use TypeScript type definitions that are automatically updated for custom steps and page objects.
+
+Writing a test in Visual Studio Code is as easy as picking a correct action and putting a parameter. It's really that nice!
+
+:::
+
+
+::: slot ui
+
+## Watch & Run Tests from UI
+
+We have a flexible interactive web runner which allows you to watch, debug, and write your tests in a web mode.
+
+Features:
+
+* Toggle headless/window mode with one click
+* See HTML snapshot of each step
+* Works with WebDriver, Puppeteer, TestCafe
+* Shows step-by-step execution
+* Integrated with your local IDE
+
+:::
+
+
+::: slot run
+
+## Print a Test
+
+Each executed step will be printed on screen when running with `--steps`
+```js
+Scenario('Checkout test', () => {
+  I.amOnPage('/checkout');
+  I.fillField('First name', 'davert');
+  I.fillField('#lastName', 'mik');
+  I.fillField('Promo code', '123345')
+  //...
+})
+```
+
+:::
+
+::: slot code
+
+## Realworld Example
+
+Can we use it for long scenarios? Sure!
+
+```js
+const faker = require('faker');                               // Use 3rd-party JS code
+
+Feature('Store');
+
+Scenario('Create a new store', async (I, login, SettingsPage) => {
+  const storeName = faker.lorem.slug();
+  login('customer');                                          // Login customer from saved cookies
+  I.mockRequest('GET', '/support-chat');                      // Mock HTTP requests with Polly
+  SettingsPage.open();                                        // Use Page objects
+  I.dontSee(storeName, '.settings');                          // Assert text not present inside an element (located by CSS)
+  I.click('Add', '.settings');                                // Click link by text inside element (located by CSS)
+  I.fillField('Store Name', storeName);                       // Fill fields by labels or placeholders
+  I.fillField('Email', faker.internet.email());
+  I.fillField('Telephone', faker.phone.phoneNumberFormat());
+  I.selectInDropdown('Status', 'Active');                     // Use custom methods
+  I.retry(2).click('Create');                                 // Auto-retry flaky step
+  I.waitInUrl('/settings/setup/stores');                      // Explicit waiter
+  I.see(storeName, '.settings');                              // Assert text present inside an element (located by CSS)
+  const storeId = await I.grabTextFrom('#store-id');          // use await to get information from browser
+  I.say(`Created a store with ${storeId}`);                   // print custom comments
+}).tag('stores');`;
+
+```
+:::

package/docs/installation.md

@@ -1,8 +1,10 @@
 ---
-id: installation
+permalink: /installation
 title: Installation
 ---
 
+# Installation
+
 ## Local
 
 Use NPM install CodeceptJS:

package/docs/locators.md

@@ -1,8 +1,10 @@
 ---
-id: locators
+permalink: /locators
 title: Locators
 ---
 
+# Locators
+
 CodeceptJS provides flexible strategies for locating elements:
 
 * [CSS and XPath locators](#css-and-xpath)
@@ -13,11 +15,11 @@ CodeceptJS provides flexible strategies for locating elements:
 
 Most methods in CodeceptJS use locators which can be either a string or an object.
 
-If the locator is an object, it should have a single element, with the key signifying the locator type (`id`, `name`, `css`, `xpath`, `link`, or `class`) and the value being the locator itself. This is called a "strict" locator.
+If the locator is an object, it should have a single element, with the key signifying the locator type (`id`, `name`, `css`, `xpath`, `link`, `react`, or `class`) and the value being the locator itself. This is called a "strict" locator.
 
 Examples:
 
-* {id: 'foo'} matches `<div id="foo">`
+* {permalink: /'foo'} matches `<div id="foo">`
 * {name: 'foo'} matches `<div name="foo">`
 * {css: 'input[type=input][value=foo]'} matches `<input type="input" value="foo">`
 * {xpath: "//input[@type='submit'][contains(@value, 'foo')]"} matches `<input type="submit" value="foobar">`
@@ -38,8 +40,17 @@ For example, here's the heuristic used for the `fillField` method:
 5. If nothing found, check if there is a label with specified text for input element.
 6. If nothing found, throw an `ElementNotFound` exception.
 
-Be warned that fuzzy locators can be significantly slower than strict locators.
-If speed is a concern, it's recommended you stick with explicitly specifying the locator type via object syntax.
+> ⚠ Be warned that fuzzy locators can be significantly slower than strict locators. If speed is a concern, it's recommended you stick with explicitly specifying the locator type via object syntax.
+
+It is recommended to avoid using implicit CSS locators in methods like `fillField` or `click`, where semantic locators are allowed.
+Use locator type to speed up search by various locator strategies.
+
+```js
+// will search for "input[type=password]" text before trying to search by CSS
+I.fillField('input[type=password]', '123456');
+// replace with strict locator
+I.fillField({ css: 'input[type=password]' }, '123456');
+```
 
 ## CSS and XPath
 
@@ -216,7 +227,7 @@ locate('button').after('.btn-cancel');
 
 ID locators are best to select the exact semantic element in web and mobile testing:
 
-* `#user` or `{ id: 'user' }` finds element with id="user"
+* `#user` or `{ permalink: /'user' }` finds element with id="user"
 * `~user` finds element with accessibility id "user" (in Mobile testing) or with `aria-label=user`.
 
 ## Custom Locators
@@ -224,7 +235,7 @@ ID locators are best to select the exact semantic element in web and mobile test
 CodeceptJS allows to create custom locator strategies and use them in tests. This way you can define your own handling of elements using specially prepared attributes of elements.
 
 What if you use special test attributes for locators such as `data-qa`, `data-test`, `test-id`, etc.
-We created [customLocator plugin](https://codecept.io/plugins#customlocator) to declare rules for locating element.
+We created [customLocator plugin](/plugins#customlocator) to declare rules for locating element.
 
 Instead of writing a full CSS locator like `[data-qa-id=user_name]` simplify it to `$user_name`.
 
@@ -237,7 +248,7 @@ I.click('$register_button');
 
 This plugin requires two options: locator prefix and actual attribute to match.
 
-> ℹ See [customLocator Plugin](https://codecept.io/plugins#customlocator) reference to learn how to set it up.
+> ℹ See [customLocator Plugin](/plugins#customlocator) reference to learn how to set it up.
 
 If you need more control over custom locators see how declare them manually without using a customLocator plugin.
 

package/docs/mobile-react-native-locators.md

@@ -46,14 +46,14 @@ You could do it just by changing `automationName` in the `helpers` section of th
 ```
 Then you could locate components using XPath expression:
 ```js
-I.tap({android: '//*[@view-tag="someButton"]', ios: '~someButton'})
+I.tap({andropermalink: /'//*[@view-tag="someButton"]', ios: '~someButton'})
 ```
 This way test would work for both platforms without any changes in code.
 To simplify things further you could write a helper function:
 ```js
 function tid(id) {
   return {
-    android: `//*[@view-tag="${id}"]`,
+    andropermalink: /`//*[@view-tag="${id}"]`,
     ios: '~' + id
   }
 }

package/docs/mobile.md

@@ -1,8 +1,10 @@
 ---
-id: mobile
+permalink: /mobile
 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.
 
@@ -17,7 +19,7 @@ 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',
+  andropermalink: /'android.widget.Button',
   ios: '//UIAApplication[1]/UIAWindow[1]/UIAButton[1]'
 });
 ```
@@ -260,7 +262,7 @@ It is often happen that mobile applications behave similarly on different platfo
 CodeceptJS provides a way to specify different locators for Android and iOS platforms:
 
 ```js
-I.click({android: '//android.widget.Button', ios: '//UIAApplication[1]/UIAWindow[1]/UIAButton[1]'});
+I.click({andropermalink: /'//android.widget.Button', ios: '//UIAApplication[1]/UIAWindow[1]/UIAButton[1]'});
 ```
 
 In case some code should be executed on one platform and ignored on others use `runOnAndroid` and `runOnIOS` methods:

package/docs/nightmare.md

@@ -1,8 +1,9 @@
 ---
-id: nightmare
+permalink: /nightmare
 title: Testing with Nightmare
 ---
 
+# Testing with Nightmare
 
 Selenium WebDriver is considered to be standard for end to end testing of web applications.
 Despite its popularity it have its drawbacks, it requires a real browser and Selenium server to control it.

package/docs/pageobjects.md

@@ -1,8 +1,10 @@
 ---
-id: pageobjects
+permalink: /pageobjects
 title: Page Objects
 ---
 
+# Page Objects
+
 UI of your web application has interaction areas which can be shared across different tests.
 To avoid code duplication you can put common locators and methods into one place.
 
@@ -185,8 +187,8 @@ class AttachFile {
 }
 
 // For inheritance
-exports.AttachFile = AttachFile
 module.exports = new AttachFile();
+module.exports.AttachFile = AttachFile;
 ```
 
 ## Page Fragments

package/docs/parallel.md

@@ -1,8 +1,10 @@
 ---
-id: parallel
+permalink: /parallel
 title: Parallel Execution
 ---
 
+# Parallel Execution
+
 CodeceptJS has two engines for running tests in parallel:
 
 * `run-workers` - which spawns [NodeJS Worker](https://nodejs.org/api/worker_threads.html) in a thread. Tests are split by scenarios, scenarios are mixed between groups, each worker runs tests from its own group.
@@ -134,7 +136,7 @@ Output is printed for all running processes. Each line is tagged with a suite an
 
 ### Hooks
 
-Hooks are available when using the `run-multiple` command to perform actions before the test suites start and after the test suites have finished. See [Hooks](https://codecept.io/hooks/#bootstrap-teardown) for an example.
+Hooks are available when using the `run-multiple` command to perform actions before the test suites start and after the test suites have finished. See [Hooks](/hooks/#bootstrap-teardown) for an example.
 
 
 ### Parallel Execution

package/docs/plugins.md

@@ -1,5 +1,7 @@
 ---
-id: plugins
+permalink: plugins
+sidebarDepth: 
+sidebar: auto
 title: Plugins
 ---
 
@@ -372,6 +374,28 @@ I.click('=sign-up'); // matches => [data-qa=sign-up]
 
 -   `config`  
 
+## pauseOnFail
+
+Automatically launches [interactive pause][4] when a test fails.
+
+Useful for debugging flaky tests on local environment.
+Add this plugin to config file:
+
+```js
+plugins: {
+  pauseOnFail: {},
+}
+```
+
+Unlike other plugins, `pauseOnFail` is not recommended to be enabled by default.
+Enable it manually on each run via `-p` option:
+
+    npx codeceptjs run -p pauseOnFail
+
+### Parameters
+
+-   `config`  
+
 ## puppeteerCoverage
 
 Dumps puppeteers code coverage after every test.
@@ -403,9 +427,9 @@ Possible config options:
 
     Links:
 
--   [https://github.com/GoogleChrome/puppeteer/blob/v1.12.2/docs/api.md#class-coverage][4]
--   [https://github.com/istanbuljs/puppeteer-to-istanbul][5]
--   [https://github.com/gotwarlost/istanbul][6]
+-   [https://github.com/GoogleChrome/puppeteer/blob/v1.12.2/docs/api.md#class-coverage][5]
+-   [https://github.com/istanbuljs/puppeteer-to-istanbul][6]
+-   [https://github.com/gotwarlost/istanbul][7]
 
 ### Parameters
 
@@ -509,7 +533,7 @@ Possible config options:
 
 ## stepByStepReport
 
-![step-by-step-report][7]
+![step-by-step-report][8]
 
 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.
@@ -554,7 +578,7 @@ This plugin allows to run webdriverio services like:
 -   browserstack
 -   appium
 
-A complete list of all available services can be found on [webdriverio website][8].
+A complete list of all available services can be found on [webdriverio website][9].
 
 ###### Setup
 
@@ -566,7 +590,7 @@ See examples below:
 
 ###### Selenium Standalone Service
 
-Install `@wdio/selenium-standalone-service` package, as [described here][9].
+Install `@wdio/selenium-standalone-service` package, as [described here][10].
 It is important to make sure it is compatible with current webdriverio version.
 
 Enable `wdio` plugin in plugins list and add `selenium-standalone` service:
@@ -585,7 +609,7 @@ Please note, this service can be used with Protractor helper as well!
 
 ##### Sauce Service
 
-Install `@wdio/sauce-service` package, as [described here][10].
+Install `@wdio/sauce-service` package, as [described here][11].
 It is important to make sure it is compatible with current webdriverio version.
 
 Enable `wdio` plugin in plugins list and add `sauce` service:
@@ -621,16 +645,18 @@ In the same manner additional services from webdriverio can be installed, enable
 
 [3]: https://codecept.io/locators#custom-locators
 
-[4]: https://github.com/GoogleChrome/puppeteer/blob/v1.12.2/docs/api.md#class-coverage
+[4]: /basics/#pause
+
+[5]: https://github.com/GoogleChrome/puppeteer/blob/v1.12.2/docs/api.md#class-coverage
 
-[5]: https://github.com/istanbuljs/puppeteer-to-istanbul
+[6]: https://github.com/istanbuljs/puppeteer-to-istanbul
 
-[6]: https://github.com/gotwarlost/istanbul
+[7]: https://github.com/gotwarlost/istanbul
 
-[7]: https://codecept.io/img/codeceptjs-slideshow.gif
+[8]: https://codecept.io/img/codeceptjs-slideshow.gif
 
-[8]: https://webdriver.io
+[9]: https://webdriver.io
 
-[9]: https://webdriver.io/docs/selenium-standalone-service.html
+[10]: https://webdriver.io/docs/selenium-standalone-service.html
 
-[10]: https://webdriver.io/docs/sauce-service.html
+[11]: https://webdriver.io/docs/sauce-service.html

package/docs/puppeteer.md

@@ -1,8 +1,10 @@
 ---
-id: puppeteer
+permalink: /puppeteer
 title: Testing with Puppeteer
 ---
 
+# Testing with Puppeteer
+
 Among all Selenium alternatives the most interesting emerging ones are tools developed around Google Chrome [DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/). And the most prominent one is [Puppeteer](https://github.com/GoogleChrome/puppeteer). It operates over Google Chrome directly without requiring additional tools like ChromeDriver. So tests setup with Puppeteer can be started with npm install only. If you want get faster and simpler to setup tests, Puppeteer would be your choice.
 
 CodeceptJS uses Puppeteer to improve end to end testing experience. No need to learn the syntax of a new tool, all drivers in CodeceptJS share the same API.
@@ -41,7 +43,7 @@ npx codeceptjs init
 
 You will be asked for a Helper to use, you should select Puppeteer and provide url of a website you are testing.
 
-> Puppeteer can also work with Firefox. [Learn how to set it up](https://codecept.io/helpers/Puppeteer-firefox)
+> Puppeteer can also work with Firefox. [Learn how to set it up](/helpers/Puppeteer-firefox)
 
 ## Configuring
 
@@ -127,7 +129,7 @@ I.seeElement({xpath: '//body/header'});
 
 ### Interactive Pause
 
-It's easy to start writing a test if you use [interactive pause](https://codecept.io/basics#debug). Just open a web page and pause execution.
+It's easy to start writing a test if you use [interactive pause](/basics#debug). Just open a web page and pause execution.
 
 ```js
 Feature('Sample Test');
@@ -191,7 +193,7 @@ within('.todoapp', () => {
 I.see('0 items left', '.todo-count');
 ```
 
-> [▶ Learn more about basic commands](https://codecept.io/basics#writing-tests)
+> [▶ 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.
 
@@ -204,7 +206,7 @@ When you run tests with Puppeteer you can control those requests by mocking them
 
 Also you can replace real request with a one explicitly defined. This is useful when you want to isolate application testing from a backend. For instance, if you don't want to save data to database, and you know the request which performs save, you can mock the request, so application will treat this as valid response, but no data will be actually saved.
 
-To mock requests enable additional helper [MockRequest](https://codecept.io/helpers/MockRequest) (which is based on Polly.js).
+To mock requests enable additional helper [MockRequest](/helpers/MockRequest) (which is based on Polly.js).
 
 ```js
 helpers: {
@@ -234,7 +236,7 @@ I.mockRequest('POST', '/api/users', { user: 'davert' });
 I.mockRequest('GET', '/api/users/1', 404, { error: 'User not found' });
 ```
 
-> See [`mockRequest` API](https://codecept.io/helpers/MockRequest#mockrequest)
+> See [`mockRequest` API](/helpers/MockRequest#mockrequest)
 
 To see `mockRequest` method in intellisense auto completion don't forget to run `codeceptjs def` command:
 

package/docs/quickstart.md

@@ -0,0 +1,130 @@
+---
+permalink: quickstart
+title: Quickstart
+layout: Section
+sidebar: true
+---
+
+::: slot sidebar
+
+#### Use WebDriver for classical Selenium setup
+
+<small>
+This gives you access to rich Selenium ecosystem and cross-browser support for majority of browsers and devices.
+</small>
+
+
+<a href="/webdriver" class="button extended" >Start with WebDriver &raquo;</a>
+
+<small>
+
+WebDriver support is implemented via [webdriverio](https://webdriver.io) library
+
+</small>
+
+---
+
+#### Use TestCafe for cross-browser testing without Selenium
+
+<small>
+TestCafe provides cross-browser support without Selenium. TestCafe tests are faster, require no extra tooling and faster than regular Selenium. However, can be less stable.
+</small>
+
+<a href="/testcafe" class="button green extended" >Start with TestCafe &raquo;</a>
+
+---
+
+* [Mobile Testing with Appium »](/mobile)
+* [Testing with Protractor »](/angular)
+* [Testing with NigthmareJS »](/nightmare)
+
+:::
+
+# Quickstart
+
+> Puppeteer is a great way to start if you need fast end 2 end tests in Chrome browser. No Selenium required!
+
+If you need cross-browser support check alternative installations with WebDriver or TestCafe &rarr;
+
+<video onclick="this.paused ? this.play() : this.pause();" src="/img/install.mp4" style="width: 100%" controls></video>
+
+If you start with empty project initialize npm first:
+
+```
+npm init -y
+```
+
+1) Install CodeceptJS with Puppeteer
+
+```
+npm install codeceptjs puppeteer --save-dev
+```
+
+
+2) Initialize CodeceptJS in current directory by running:
+
+```
+npx codeceptjs init
+```
+
+(use `node node_modules/.bin/codeceptjs` if you have issues with npx)
+
+3) Answer questions. Agree on defaults, when asked to select helpers choose **Puppeteer**.
+
+```
+? What helpers do you want to use?
+ ◯ WebDriver
+ ◯ Protractor
+❯◉ Puppeteer
+ ◯ Appium
+ ◯ Nightmare
+ ◯ FileSystem
+ ```
+
+4) Create First Test.
+
+```
+npx codeceptjs gt
+```
+
+5) Enter a test name. Open a generated file in your favorite JavaScript editor.
+
+```js
+Feature('My First Test');
+
+Scenario('test something', (I) => {
+
+});
+```
+
+6) Write a simple scenario
+
+```js
+Feature('My First Test');
+
+Scenario('test something', (I) => {
+  I.amOnPage('https://github.com');
+  I.see('GitHub');
+});
+```
+
+7) Run a test:
+
+```
+npx codeceptjs run --steps
+```
+
+The output should be similar to this:
+
+```bash
+My First Test --
+  test something
+     I am on page "https://github.com"
+     I see "GitHub"
+ ✓ OK
+ ```
+
+> [▶ Next: CodeceptJS Basics](/basics/)
+
+> [▶ Next: CodeceptJS with Puppeteer](/puppeteer/)
+