0.0.5 • Published 6 years ago
testcafe-serverless-cli v0.0.5
testcafe-serverless-cli
Deploy lambdas and resources:
npx testcafe-serverless-cli init --accessKeyId=XXXXXXXXXXXX --secretAccessKey=XXXXXXXXXXXXRun testcafe tests:
npx testcafe-serverless-cli run --accessKeyId=XXXXXXXXXXXX --secretAccessKey=XXXXXXXXXXXX --testcafeDir=/path/to/test-cafe-project --concurrency=1You can pass the following options to the npx testcafe-serverless-cli run [options] function.
| Parameter | Type | Description | Default |
|---|---|---|---|
skipJsErrors | Boolean | Defines whether to continue running a test after a JavaScript error occurs on a page (true), or consider such a test failed (false). | false |
skipUncaughtErrors | Boolean | Defines whether to continue running a test after an uncaught error or unhandled promise rejection occurs on the server (true), or consider such a test failed (false). | false |
selectorTimeout | Number | Specifies the time (in milliseconds) within which selectors make attempts to obtain a node to be returned. See Selector Timeout. | 10000 |
assertionTimeout | Number | Specifies the time (in milliseconds) within which TestCafe makes attempts to successfully execute an assertion if a selector property or a client function was passed as an actual value. See Smart Assertion Query Mechanism. | 3000 |
pageLoadTimeout | Number | Specifies the time (in milliseconds) TestCafe waits for the window.load event to fire after the DOMContentLoaded event. After the timeout passes or the window.load event is raised (whichever happens first), TestCafe starts the test. You can set this timeout to 0 to skip waiting for window.load. | 3000 |
speed | Number | Specifies the test execution speed. A number between 1 (fastest) and 0.01 (slowest). If an individual action's speed is also specified, the action speed setting overrides the test speed. | 1 |
stopOnFirstFail | Boolean | Defines whether to stop a test run if a test fails. You do not need to wait for all the tests to finish to focus on the first error. | false |