codeceptjs 3.5.12-beta.3 → 3.5.12-beta.5

package/docs/wiki/Books-&-Posts.md

@@ -0,0 +1,27 @@
+### [Practical End 2 End Testing with CodeceptJS](https://leanpub.com/codeceptjs/)
+
+A book by **Paul Vincent Beigang**
+
+[![](https://user-images.githubusercontent.com/220264/58870454-e2e8ce80-86c8-11e9-868e-7deefdde47ce.png)](https://leanpub.com/codeceptjs/)
+
+#### Contents:
+
+1. Preparation for End 2 End Testing with CodeceptJS
+1. Setup CodeceptJS with WebdriverIO
+1. Create Your First CodeceptJS Test
+1. Run Your First CodeceptJS Test Locally
+1. Run Test on BrowserStack Against with the Safari Browser
+1. How to Debug & Fix a Failing E2E Test
+1. Run a CodeceptJS Test in GitLab´s Continuous Integration (CI) Environment
+1. Delicious Test Reports With Allure
+
+### Posts
+
+A list of good educational posts about CodeceptJS
+
+* [QA Automation From Zero-to-Hero with CodeceptJS End-to-End Testing](https://medium.com/@dan.ryan.emmons/qa-automation-from-zero-to-hero-with-codeceptjs-end-to-end-testing-719db9d6ff5c) by Dan Emmons
+* [Effective End2End Tests with CodeceptJS](https://hackernoon.com/effective-end-2-end-testing-in-javascript-with-codeceptjs-37c8d7d6a928) by @davertmik
+* [Customizing CodeceptJS Skeleton](https://medium.com/@successivetech/codeceptjs-skeleton-9ba86d3b45ec)
+* [Running End to End tests as Google Cloud Functions](https://hackernoon.com/running-end-to-end-tests-as-google-cloud-functions-f5e34ffc3984)
+* [End-To-End Testing With CodeceptJS](https://www.monterail.com/blog/end-to-end-testing-with-codeceptjs) by Piotr Michalski
+* [Getting started with CodeceptJS and Selenium WebDriver](https://medium.com/@garrettvorce/getting-started-with-selenium-and-codeceptjs-c0698e8df677)

package/docs/wiki/Community-Helpers-&-Plugins.md

@@ -0,0 +1,53 @@
+Here is the list of helpers created by our community.
+Please **add your own** by editing this page.
+## Webhooks
+
+* [codeceptjs-webhook-helper](https://github.com/onemolegames/codeceptjs-webhook-helper) - to check webhook calls during the tests.
+
+## Email Checking
+
+* [MailCatcher](https://gist.github.com/schmkr/026732dfa1627b927ff3a08dc31ee884) - to check emails via Mailcatcher locally.
+* [codeceptjs-mailhog-helper](https://github.com/tsuemura/codeceptjs-mailhog-helper) - to check emails via Mailhog locally.
+* [codeceptjs-testmailapp-helper](https://github.com/pavkam/codeceptjs-testmailapp-helper) - to check emails via Testmail.app service.
+* [codeceptjs-mailosaurhelper](https://github.com/yurkovychv/codeceptjs-mailosaur) - to check emails via [Mailosaur](https://mailosaur.com/) service.
+
+## Data Sources
+
+* [codeceptjs-httpmock](https://github.com/testphony/codeceptjs-httpMock) -  a helper which wraps mockttp library to manage http mock in tests.
+* [codeceptjs-http](https://github.com/testphony/codeceptjs-http) - a helper which wraps then-request library to process HTTP requests. It's alternative helper that provides more flexible request management.
+* [codeceptjs-dbhelper](https://github.com/thiagodp/codeceptjs-dbhelper) - allows you to execute queries or commands to databases using database-js. 
+
+## Cloud Providers
+* [codeceptjs-saucehelper](https://github.com/puneet0191/codeceptjs-saucehelper/) - a helper which updates `Test Names` & `Test Results` on Saucelabs 
+* [codeceptjs-bshelper](https://github.com/PeterNgTr/codeceptjs-bshelper) - a helper which updates `Test Names` & `Test Results` on Browserstack 
+* [codeceptjs-tbhelper](https://github.com/testingbot/codeceptjs-tbhelper) - a helper which updates `Test Names` & `Test Results` on TestingBot 
+
+## Visual-Testing
+* [codeceptjs-resemblehelper](https://github.com/puneet0191/codeceptjs-resemblehelper) - a helper which helps with visual testing using resemble.js. 
+* [codeceptjs-applitoolshelper](https://www.npmjs.com/package/codeceptjs-applitoolshelper) - a helper which helps interaction with [Applitools](https://applitools.com)
+* [codeceptjs-pixelmatchhelper](https://github.com/stracker-phil/codeceptjs-pixelmatchhelper) - a helper that integrates pixelmatch for visual testing. 
+
+## Reporters
+* [codeceptjs-rphelper](https://github.com/reportportal/agent-js-codecept) is a CodeceptJS helper which can publish tests results on ReportPortal after execution.
+* [codeceptjs-xray-helper](https://www.npmjs.com/package/codeceptjs-xray-helper) is a CodeceptJS helper which can publish tests results on [XRAY](https://confluence.xpand-it.com/display/XRAYCLOUD/Import+Execution+Results+-+REST).
+* [codeceptjs-xray-cloud-helper](https://www.npmjs.com/package/codeceptjs-xray-cloud-helper) is a helper that automatically retrieves the result of CodeceptJS tests and sends them to XRAY/JIRA(cloud version) via [XRAY Cloud API](https://docs.getxray.app/display/XRAYCLOUD/Import+Execution+Results+-+REST+v2#ImportExecutionResultsRESTv2-XrayJSONresults).
+* [codeceptjs-slack-reporter](https://www.npmjs.com/package/codeceptjs-slack-reporter) Get a Slack notification when one or more scenarios fail.
+* [codeceptjs-browserlogs-plugin](https://github.com/pavkam/codeceptjs-browserlogs-plugin) Record the browser logs for failed tests.
+* [codeceptjs-testrail](https://github.com/PeterNgTr/codeceptjs-testrail) - a plugin to integrate with [Testrail](https://www.gurock.com/testrail)
+
+## Browser request control
+* [codeceptjs-resources-check](https://github.com/luarmr/codeceptjs-resources-check) Load a URL with Puppeteer and listen to the requests while the page is loading. Enabling count the number or check the sizes of the requests.
+
+## Assertion & Validations
+* [codeceptjs-chai](https://www.npmjs.com/package/codeceptjs-chai) is a CodeceptJS helper which wraps
+[chai](https://www.chaijs.com/) library to complete chai assertion steps with CodeceptJS logging.
+
+## Other
+
+* [codeceptjs-cmdhelper](https://github.com/thiagodp/codeceptjs-cmdhelper) allows you to run commands in the terminal/console
+* [eslint-plugin-codeceptjs](https://www.npmjs.com/package/eslint-plugin-codeceptjs) Eslint rules for CodeceptJS.
+* [codeceptjs-datalayer-helper](https://github.com/kobenguyent/codeceptjs-datalayer-helper) CodeceptJS DataLayer helper helps you to get the datalayer JavaScript array that is used to store information and send this data to the tag manager.
+* [codeceptjs-a11y-helper](https://github.com/kobenguyent/codeceptjs-a11y-helper) accessibility tests integrated with CodeceptJS - Playwright-axe
+* [codeceptjs-lighthouse-helper](https://github.com/kobenguyent/codeceptjs-lighthouse-helper) lighthouse audit integrated with CodeceptJS - Playwright
+* [Snowplow Data analytics](https://www.npmjs.com/package/@viasat/codeceptjs-snowplow-helper) - Test your Snowplow events implementations with CodeceptJS and Snowplow Micro.
+* [codeceptjs-failure-logger](https://github.com/kobenguyent/codeceptjs-failure-logger) - Log failed CodeceptJS tests to file

package/docs/wiki/Converting-Playwright-to-Istanbul-Coverage.md

@@ -0,0 +1,61 @@
+How to convert `playwright` coverage format to `istanbul` coverage
+
+To convert coverage generated from `playwright` to `istanbul` coverage, you first need to install
+- [`v8-to-istanbul`](https://www.npmjs.com/package/v8-to-istanbul)
+
+Once installed, convert the coverage to a format which `istanbul` can recognize, by writing a script as shown below.
+
+```ts
+import glob from 'glob'
+import v8toIstanbul from 'v8-to-istanbul'
+let coverage
+
+import fs from 'fs'
+
+const coverageFolder = `${process.cwd()}/coverage`
+
+async function isExists(path) {
+    try {
+        await fs.access(path, null)
+        return true
+    } catch {
+        return false
+    }
+}
+
+glob.sync(process.cwd() + '/output/coverage/**/').forEach(item => {
+    const directory = fs.opendirSync(item)
+    let file
+    while ((file = directory.readSync()) !== null) {
+        if (file && file.name.includes('.coverage.json') === true) {
+            const fileName = file.name
+            if (fileName) {
+                coverage = require(`${process.cwd()}/output/coverage/${fileName}`)
+            }
+        }
+    }
+    directory.closeSync()
+})
+
+void (async () => {
+    for (const entry of coverage) {
+        // Used to get file name
+        const file = entry.url.match(/(?:http(s)*:\/\/.*\/)(?<file>.*)/)
+
+        const converter = v8toIstanbul(file.groups.file, 0, {
+            source: entry.source,
+        })
+
+        await converter.load()
+        converter.applyCoverage(entry.functions)
+
+        // Store converted coverage file which can later be used to generate report
+        const exist = await isExists(coverageFolder)
+        if (!exist) {
+            fs.mkdirSync(coverageFolder, {recursive: true})
+        }
+
+        await fs.writeFileSync(`${coverageFolder}/final.json`, JSON.stringify(converter.toIstanbul(), null, 2))
+    }
+})()
+```

package/docs/wiki/Examples.md

@@ -0,0 +1,145 @@
+## [TodoMVC Examples](https://github.com/codecept-js/examples)
+
+![](https://github.com/codecept-js/examples/raw/master/todo.png)
+
+Playground repository where you can run tests in different helpers on a basic single-page website.
+
+Tests repository demonstrate usage of
+
+* Playwright helper
+* Puppeteer helper
+* WebDriver helper
+* TestCafe plugin
+* Toggle headless mode with env variables
+* PageObjects
+* Cucumber syntax
+
+## [Basic Examples](https://github.com/Codeception/CodeceptJS/tree/master/examples)
+
+CodeceptJS repo contains basic tests (both failing and passing) just to show how it works.
+Our team uses it to test new features and run simple scenarios.
+
+## [CodeceptJS Cucumber E2E Framework](https://github.com/gkushang/codeceptjs-e2e)
+
+This repository contains complete E2E framework for CodeceptJS with Cucumber and SauceLabs Integration
+
+* CodecepJS-Cucumber E2E Framework
+* Saucelabs Integration
+* Run Cross Browser tests in Parallel on SauceLabs with a simple command
+* Run tests on `chrome:headless`
+* Page Objects
+* `Should.js` Assertion Library
+* Uses `wdio` service (selenium-standalone, sauce)
+* Allure HTML Reports
+* Uses shared Master configuration
+* Sample example and feature files of GitHub Features
+
+## [Enterprise Grade Tests](https://github.com/uc-cdis/gen3-qa)
+
+Complex testing solution by [Gen3](https://github.com/uc-cdis/gen3-qa) 
+
+Includes 
+
+* classical CodeceptJS tests
+* BDD tests
+* Jenkins integration
+* Complex Before/BeforeSuite scripts and more
+
+## [Testing Single Page Application](https://github.com/bugiratracker/codeceptjs-demo)
+
+End 2 end tests for Task management app (currently offline).
+
+Tests repository demonstrate usage of
+
+* Puppeteer helper
+* ApiDataFactory helper
+* autoLogin plugin
+* Dynamic config with profiles
+
+## [Practical E2E Tests](https://gitlab.com/paulvincent/codeceptjs-e2e-testing)
+
+Examples from the book [Practical End 2 End Testing with CodeceptJS](https://leanpub.com/codeceptjs/) by **Paul Vincent Beigang**. 
+
+This repository demonstrates usage of:
+
+* dynamic config with profiles
+* testing WYSIWYG editor
+* GitLab CI
+
+## [Amazon Tests v2](https://gitlab.com/thanhnguyendh/codeceptjs-wdio-services)
+
+Testing Amazon website using Selenium WebDriver.
+
+This repository demonstrates usage of:
+
+* WebDriver helper
+* Page Objects
+* wdio services (selenium-standalone)
+* Parallel execution
+* GitLab CI setup
+
+## [Tests with Docker Compose](https://github.com/mathesouza/codeceptjs-docker-compose)
+
+Running CodeceptJS tests with Docker Compose
+
+This repository demonstrates usage of:
+
+* CodeceptJS Docker image 
+* WebDriver helper
+* Allure plugin
+
+
+## [AngularJS Example Tests](https://github.com/armno/angular-e2e-codeceptjs-example)
+
+Based on [Setting up End-to-End Testing in Angular Project with CodeceptJS](https://medium.com/@armno/setting-up-end-to-end-testing-in-angular-project-with-codeceptjs-ac1784de3420) post by Armno Prommarak.
+
+This repository demonstrates usage of
+
+* Puppeteer helper
+* Working with Angular CLI
+* Reports with Mochawesome helper
+
+## [REST Example Tests](https://github.com/PeterNgTr/codeceptjs-rest-demo)
+
+This repository demonstrates usage of
+
+* REST helper
+
+## [Automation Starter](https://github.com/sjorrillo/automation-starter)
+
+The purpose of this application is for learning the basics and how to use good practices and useful tools in automation.
+
+* Puppeteer helper
+* Working with gherkin, also it has type definitions and to be able to use them inside when, given and then make sure you add `declare function inject(): { I: CodeceptJS.I, [key: string]: any; };`in the `steps.d.ts`file 
+* Linting `airbnb-base`, `codeceptjs/codeceptjs` and full ES6 support
+
+## [Example for using: Puppeteer, Gherkin, Allure with parallel execution](https://github.com/SchnuckySchuster/codeceptJSExample)
+
+This is a ready to use example that shows how to integrate CodeceptJS with Puppeteer and Allure as reporting tool.
+
+* detailed ReadMe
+* tests written in cucumber alongside tests written in the codeceptJS DSL
+* puppeteer helper example
+* test steps, pages, fragments
+* examples for sequential and parallel execution
+* generation of allure test results  
+
+## [Example for Advanced REST API testing: TypeScript, Axios, CodeceptJS, Jest Expect, Docker, Allure, Mock-Server, Prettier + Eslint, pre-commit, Jest Unit Tests ](https://github.com/EgorBodnar/rest-axios-codeceptjs-allure-docker-test-example)
+One button example with built-in mocked backend. 
+
+If you already have a UI testing solution based on the CodeceptJS and you need to implement advanced REST API testing you can just extend your existing framework. Use this implementation as an example.
+This is necessary if all integrations with TMS and CI/CD are already configured, and you do not want to reconnect and configure the plugins and libraries used for the new test runner. Use CodeceptJS!
+
+* Easy run
+* Detailed README
+* Well documented mocked backend's REST API endpoints
+* HTTP request client with session support and unit tests
+* Exemplary code control
+* Ready to launch in a CI/CD system as is
+* OOP, Test data models and builders, endpoint decorators
+
+## [Playwright fun with CodeceptJS](https://github.com/PeterNgTr/codeceptjs-playwright-fun)
+* Tests are written in TS
+* CI/CD with Github Actions
+* Page Object Model is applied
+* ReportPortal Integration

package/docs/wiki/Google-Summer-of-Code-(GSoC)-2020.md

@@ -0,0 +1,68 @@
+### About
+GSoC is an international annual program in which Google awards stipends to university students who successfully complete a requested coding project during the summer. 
+
+Codecept-JS has decided to apply to participate in GSoC 2020, Please note that the final list of GSoC 2020 organizations will be announced on 22nd Feb 2020.  
+
+To read more about the program please visit [GSoC Program](https://summerofcode.withgoogle.com/)
+
+The timeline for the program can be found on [Official Program Timeline](https://summerofcode.withgoogle.com/how-it-works/#timeline)
+
+### Contact Information
+
+For all the students who are interested in working with Codecept-JS organization for GSoC 2020, you can start by reaching out to our organization team by posting your interest in our [Forum](https://codecept.discourse.group/)
+
+Read about the Project on our [Official Project Website](https://codecept.io/)
+
+You can also join our Community Slack, which is used for community conversation, our GSoC team will be available on slack, we will have dedicated channel for GSoC Students and Projects, join [here](http://bit.ly/chat-codeceptjs)
+
+### Student Information
+
+If you are a student and are interested in participating, the following is useful information. 
+
+#### Proposal Guidelines
+Before applying as a Codeceptjs Contributor, we suggest you review the points below. It can help you with creating a strong Proposal.
+
+1. Read about Codeceptjs on our [Official Website](https://codecept.io/)
+2. Setup Codeceptjs on your working system, and then Go through the list of open issues on our [Github Repo](https://github.com/Codeception/CodeceptJS/issues), try to help us with fixing some of them, or help in testing existing PR's from our developers. 
+3. Go through the guides available on our official website, understand how our helpers work and check the list of current helpers on our organization [Github](https://github.com/codecept-js)
+
+#### Application Template
+
+If you are planning to send us a proposal, please make sure you have addressed the following elements:
+
+1. About you (your background, experience, education, hobbies)
+2. Project background (current state of what exist)
+3. Design/description of work
+4. Benefit of your work to the project users and developers
+5. Deliverables
+6. Scheduling
+7. Other commitments (i.e., exams, part time work, holidays, lectures, etc.)
+8. Community engagement (involvement, sample PR's, forum discussions, other open-source involvement)
+
+### Idea's for GSoC 2020
+
+#### Improve Visual Testing Support in Codeceptjs
+CodeceptJS has a visual testing helper which is based on resemble.js, instructions to set up and use the helper can be found [here](https://github.com/codecept-js/codeceptjs-resemblehelper)
+
+We have several improvements we want to make to our helper, here is the list. 
+1. Add Support for Allure Reporter
+2. Add Support for Visual Testing with [Codecept UI](https://codecept.io/ui/) 
+3. Support for [Workers](https://codecept.io/parallel/)
+
+Knowledge Prerequisite: Github, Nodejs, CodeceptJS, Resemble.js
+
+Difficulty: Medium
+
+Possible Mentors: Puneet Kala, Koushik Mohan
+
+#### Improve Codecept UI
+CodeceptJS has an interactive, graphical test runner, which is called CodeceptUI. It works on Browsers and helps in managing tests. 
+We need help with improving the CodeceptUI project, fixing existing issues. 
+1. To get started, please read about CodeceptUI [here](https://codecept.io/ui/)
+2. To get your hands on the code, you can check out the Repo [here](https://github.com/codecept-js/ui), look at the list of open issues and start with fixing them. 
+
+Knowledge Prerequisite: Github, CodeceptJS, JS, VueJS, Express.js, WebSockets, NodeJS
+
+Difficulty: Medium
+
+Possible Mentors: Michael Bodnarchuk, Paul 

package/docs/wiki/Home.md

@@ -0,0 +1,16 @@
+Wiki Pages contain community content which is partly copied into the website.
+
+* :toolbox:  [Community Helpers & Plugins](https://github.com/codeceptjs/CodeceptJS/wiki/Community-Helpers-&-Plugins) - collection of community-driven plugins and helpers (synced with website).
+* :eyes:  [Examples](https://github.com/codeceptjs/CodeceptJS/wiki/Examples) - collection of CodeceptJS sample projects (synced with website).
+* :book: [Books & Posts](https://github.com/Codeception/CodeceptJS/wiki/Books-&-Posts) - posts about CodeceptJS (synced with website).
+* :tv: [Videos](https://github.com/codeceptjs/CodeceptJS/wiki/Videos) - videos on CodeceptJS (synced with website).
+Add your own entries to these lists.
+
+Other useful links:
+* [Official Site](http://codecept.io)
+* [Roadmap](https://github.com/Codeception/CodeceptJS/wiki/Roadmap)
+* [Code on Github](https://github.com/Codeception/CodeceptJS)
+* [Change log](https://github.com/Codeception/CodeceptJS/blob/master/CHANGELOG.md)
+* [GSoC](https://github.com/Codeception/CodeceptJS/wiki/Google-Summer-of-Code-(GSoC)-2020)
+
+

package/docs/wiki/Migration-to-Appium-v2---CodeceptJS.md

@@ -0,0 +1,83 @@
+# Migrating from Appium 1.x to Appium 2.x
+This document is a guide for those who are using Appium 1.x and wish to migrate to Appium 2.x. It contains a list of breaking changes and how to migrate your environments or test suites to ensure compatibility with Appium 2.0.
+
+# Overview of Appium 2.0
+Appium 2.0 is the most major new release of Appium in over 5 years. The changes in Appium 2.0 are not primarily related to changes in automation behaviors for specific platforms. Instead, Appium 2.0 reenvisions Appium as a platform where "drivers" (code projects that introduce support for automation of a given platform) and "plugins" (code projects that allow for overriding, altering, extending, or adding behaviors to Appium) can be easily created and shared.
+
+At the same time, the Appium project is taking the opportunity to remove many old and deprecated bits of functionality.
+
+Together these do introduce a few breaking changes to how Appium is installed, how drivers and various features are managed, and protocol support. These are detailed below.
+
+# Breaking Changes
+Here we call out the breaking changes and what you need to do to account for them.
+
+## ‼ Default server base path
+With Appium 1.x, the server would accept commands by default on http://localhost:4723/wd/hub. The /wd/hub base path was a legacy convention from the days of migrating from Selenium 1 to Selenium 2, and is no longer relevant. As such the default base path for the server is now /. If you want to retain the old behaviour, you can set the base path via a command line argument as follows:
+
+`appium --base-path=/wd/hub`
+
+## ‼ Installing drivers during setup
+When you installed Appium 1.x, all available drivers would be installed at the same time as the main Appium server. This is no longer the case. Simply installing Appium 2.0 (e.g., by npm install -g appium@next), will install the Appium server only, but no drivers. To install drivers, you must instead use the new [Appium extension CLI](https://appium.github.io/appium/docs/en/2.0/cli/extensions/). For example, to install the latest versions of the XCUITest and UiAutomator2 drivers, after installing Appium you would run the following commands:
+
+```
+appium driver install uiautomator2,xcuitest     # installs the latest driver version  
+```
+At this point, your drivers are installed and ready. There's a lot more you can do with this CLI so be sure to check out the docs on it. If you're running in a CI environment or want to install Appium along with some drivers all in one step, you can do so using some special flags during install, for example:
+
+`npm install --global appium --drivers=xcuitest,uiautomator2`
+This will install Appium and the two drivers for you in one go. Please uninstall any existing Appium 1.x npm packages (with npm uninstall -g appium) if you get an installation or startup error.
+
+## ‼ Capabilities
+One significant difference between old and new protocols is in the format of capabilities. Previously called "desired capabilities", and now called simply "capabilities", there is now a requirement for a so-called "vendor prefix" on any non-standard capabilities. The list of standard capabilities is given in the [WebDriver Protocol spec](https://www.w3.org/TR/webdriver/#capabilities), and includes a few commonly used capabilities such as browserName and platformName.
+
+These standard capabilities continue to be used as-is. All other capabilities must include a "vendor prefix" in their name. A vendor prefix is a string followed by a colon, such as appium:. Most of Appium's capabilities go beyond the standard W3C capabilities and must therefore include vendor prefixes (we recommend that you use appium: unless directed otherwise by documentation). For example:
+
+```
+`appium:app`
+`appium:noReset`
+`appium:deviceName`
+```
+
+This requirement may or may not be a breaking change for your test suites when targeting Appium 2.0. If you're using an updated Appium client (at least one maintained by the Appium team), the client will add the appium: prefix for you on all necessary capabilities automatically. New versions of [Appium Inspector](https://github.com/appium/appium-inspector) will also do this. Cloud-based Appium providers may also do this. So simply be aware that if you get any messages to the effect that your capabilities lack a vendor prefix, this is how you solve that problem.
+
+To make everyone's lives a bit easier with CodeceptJS, you don't need to update your capabilities to include "vendor prefix", CodeceptJS does it for you out of the box.
+
+## ‼ WebdriverIO upgrade
+CodeceptJS should be installed with webdriverio support, as the moment of testing, `webdriverio@8.6.3` works seamlessly:
+```bash
+npm install codeceptjs webdriverio@8.6.3 --save
+```
+
+## ‼ CodeceptJS configuration
+
+```
+...
+        appiumV2: true, // set this to true to try out appium 2.x
+        'app': `${process.cwd()}/build/Monefy_Pro_v1.15.0.apk`,
+        'platform': 'android',
+        'device': 'emulator',
+        'port': DEFAULT_PORT,
+        'path': '/wd/hub',
+        browser: '',
+        desiredCapabilities: {
+            'appPackage': data.packageName,
+            'deviceName': process.env.DEVICE || 'Emulator',
+            'platformName': process.env.PLATFORM || 'android',
+            'platformVersion': process.env.OS_VERSION || '11.0',
+            'automationName': process.env.ENGINE || 'UIAutomator2',
+            'avd': process.env.UDID || 'Pixel_XL_API_30',
+            'newCommandTimeout': 300000,
+            'androidDeviceReadyTimeout': 300000,
+            'androidInstallTimeout': 90000,
+            'appWaitDuration': 300000,
+            'autoGrantPermissions': true,
+            'gpsEnabled': true,
+            'isHeadless': false,
+            'noReset': false,
+            'noSign': true,
+        }
+...
+```
+
+
+Demo project to try with Appium v2: https://github.com/kobenguyent/thanh-nguyen/tree/main/task2

package/docs/wiki/Release-Process.md

@@ -0,0 +1,24 @@
+This is the guide for maintainers:
+
+## Release Process
+
+1. Pull the latest changes from main branch for release stream e.g. 3.x
+2. Create a release branch and switch to it by `git checkout -b release-x.x.x`
+3. Update version in `package.json`
+4. Go through the commits for the new release and add them to the CHANGELOG.md: 
+  * Changelog should be written for humans (not for robots). 
+  * Use simple wording explaining what the change is, how to use a new feature (maybe with a code example) and mention the related issue. 
+  * When using `#123` a link for issue #123 will be automatically added. 
+  * A contributor must be mentioned. We use GitHub names with `@` prefix. A link to user profile is automatically added.
+5. Run `./runok.js docs` to build documentation
+6. Commit all changes, push and create a PR
+7. Check that all tests pass and merge your PR
+8. Run `./runok.js release` to publish latest release. The website will be updated.
+  * To update version for patch release: `./runok.js release patch`
+  * To update version for minor release: `./runok.js release minor`
+9. Post announcements in Twitter & Slack
+
+## Updating the website
+
+* Run `./runok.js docs:helpers` to build docs from helpers
+* Run `./runok.js publish:site` to update a website

package/docs/wiki/Roadmap.md

@@ -0,0 +1,23 @@
+[Upcoming releases](https://github.com/Codeception/CodeceptJS/projects)
+
+## Backlog
+
+* Shadow-DOM locator integration with webdriverio 5.x
+* Cypress integration
+* Reuse a single browser session while writing tests
+
+---
+
+## Done
+
+To make those features implemented, consider [sponsoring CodeceptJS](https://github.com/Codeception/CodeceptJS/issues/1462).
+
+* ~GraphQL helper~
+* ~Cypress-like Development mode:~
+  * ~UI for selecting and executing tests~
+* ~[Detox](https://github.com/wix/Detox) integration for React Native and mobile testing~ 
+* ~TestCafe integration~
+* ~Parallel execution via workers (improves CPU consumation, reporting)~
+* ~Mock Request/Response in Puppeteer helper via [PollyJS](https://github.com/Netflix/pollyjs).~
+* Update BDD/Gherkin support to Gherkin version 6 specification
+  * [See Version 6.0.13](https://github.com/cucumber/cucumber/blob/master/gherkin/CHANGELOG.md#6013---2018-09-25)