codeceptjs 3.5.2 → 3.5.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +44 -0
- package/README.md +4 -5
- package/docs/basics.md +1 -2
- package/docs/build/Playwright.js +461 -0
- package/docs/changelog.md +44 -0
- package/docs/custom-helpers.md +2 -2
- package/docs/data.md +6 -2
- package/docs/docker.md +2 -3
- package/docs/helpers/Playwright.md +289 -150
- package/docs/helpers/Protractor.md +1709 -0
- package/docs/installation.md +1 -1
- package/docs/mobile.md +0 -2
- package/docs/plugins.md +0 -2
- package/docs/quickstart.md +0 -1
- package/docs/testcafe.md +1 -1
- package/docs/webdriver.md +0 -2
- package/lib/command/init.js +1 -1
- package/lib/helper/Playwright.js +461 -0
- package/lib/plugin/standardActingHelpers.js +0 -2
- package/lib/plugin/wdio.js +0 -1
- package/lib/recorder.js +2 -1
- package/package.json +4 -6
- package/typings/index.d.ts +0 -1
- package/typings/promiseBasedTypes.d.ts +127 -0
- package/typings/types.d.ts +127 -25
- package/docs/nightmare.md +0 -223
package/docs/docker.md
CHANGED
|
@@ -13,7 +13,7 @@ CodeceptJS runner is available inside container as `codeceptjs`.
|
|
|
13
13
|
|
|
14
14
|
### Locally
|
|
15
15
|
|
|
16
|
-
You can execute CodeceptJS with Puppeteer
|
|
16
|
+
You can execute CodeceptJS with Puppeteer locally with no extra configuration.
|
|
17
17
|
|
|
18
18
|
```sh
|
|
19
19
|
docker run --net=host -v $PWD:/tests codeceptjs/codeceptjs
|
|
@@ -56,7 +56,7 @@ services:
|
|
|
56
56
|
|
|
57
57
|
### Linking Containers
|
|
58
58
|
|
|
59
|
-
If using the
|
|
59
|
+
If using the WebDriver driver, link the container with a Selenium Standalone docker container with an alias of `selenium`. Additionally, make sure your `codeceptjs.conf.js` contains the following to allow CodeceptJS to identify where Selenium is running.
|
|
60
60
|
|
|
61
61
|
```javascript
|
|
62
62
|
...
|
|
@@ -80,7 +80,6 @@ $ docker run -it --rm -v /<path_to_codeceptjs_test_dir>/:/tests/ --link selenium
|
|
|
80
80
|
|
|
81
81
|
You may run use `-v $(pwd)/:tests/` if running this from the root of your CodeceptJS tests directory.
|
|
82
82
|
_Note: The output of your test run will appear in your local directory if your output path is `./output` in the CodeceptJS config_
|
|
83
|
-
_Note: If running with the Nightmare driver, it is not necessary to run a selenium docker container and link it. So `--link selenium-chrome:selenium` may be omitted_
|
|
84
83
|
|
|
85
84
|
### Build
|
|
86
85
|
|