Update testcafe to the latest version 🚀

greenkeeper[bot] commented 6 years ago

Version 0.21.0 of testcafe was just published.

Dependency	testcafe
Current Version	0.20.5
Type	devDependency

The version 0.21.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of testcafe.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Release Notes

v0.21.0

v0.21.0 (2018-8-2)

Enhancements

⚙️ Test Web Pages Served Over HTTPS (#1985)

Some browser features (like Service Workers, Geolocation API, ApplePaySession, or SubtleCrypto) require a secure origin. This means that the website should use the HTTPS protocol.

Starting with v0.21.0, TestCafe can serve proxied web pages over HTTPS. This allows you to test pages that require a secure origin.

To enable HTTPS when you use TestCafe through the command line, specify the --ssl flag followed by the HTTPS server options. The most commonly used options are described in the TLS topic in the Node.js documentation.

testcafe --ssl pfx=path/to/file.pfx;rejectUnauthorized=true;...

When you use a programming API, pass the HTTPS server options to the createTestCafe method.

'use strict';

const createTestCafe        = require('testcafe');
const selfSignedSertificate = require('openssl-self-signed-certificate');
let runner                  = null;

const sslOptions = {
    key:  selfSignedSertificate.key,
    cert: selfSignedSertificate.cert
};

createTestCafe('localhost', 1337, 1338, sslOptions)
    .then(testcafe => {
        runner = testcafe.createRunner();
    })
    .then(() => {
        return runner
            .src('test.js')

            // Browsers restrict self-signed certificate usage unless you
            // explicitly set a flag specific to each browser.
            // For Chrome, this is '--allow-insecure-localhost'.
            .browsers('chrome --allow-insecure-localhost')
            .run();
    });

See Connect to TestCafe Server over HTTPS for more information.

⚙️ Construct Screenshot Paths with Patterns (#2152)

You can now use patterns to construct paths to screenshots. TestCafe provides a number of placeholders you can include in the path, for example, ${DATE}, ${TIME}, ${USERAGENT}, etc. For a complete list, refer to the command line --screenshot-path-pattern flag description.

You specify a screenshot path pattern when you run tests. Each time TestCafe takes a screenshot, it substitutes the placeholders with actual values and saves the screenshot to the resulting path.

The following example shows how to specify a screenshot path pattern through the command line:

testcafe all test.js -s screenshots -p "${DATE}_${TIME}/test-${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}.png"

When you use a programming API, pass the screenshot path pattern to the runner.screenshots method.

runner.screenshots('reports/screenshots/', true, '${TEST_INDEX}/${OS}/${BROWSER}-v${BROWSER_VERSION}/${FILE_INDEX}.png');

⚙️ Add Info About Screenshots and Quarantine Attempts to Custom Reports (#2216)

Custom reporters can now access screenshots' data and the history of quarantine attempts (if the test run in the quarantine mode).

The following information about screenshots is now available:

the path to the screenshot file,
the path to the thumbnail image,
the browser's user agent,
the quarantine attempt number (if the screenshot was taken in the quarantine mode),
whether the screenshot was taken because the test failed.

If the test was run in the quarantine mode, you can also determine which attempts failed and passed.

Refer to the reportTestDone method description for details on how to access this information.

Bug Fixes

HTML5 drag events are no longer simulated if event.preventDefault is called for the mousedown event (#2529)
File upload no longer causes an exception when there are several file inputs on the page (#2642)
File upload now works with inputs that have the required attribute (#2509)
The load event listener is no longer triggered when added to an image (testcafe-hammerhead/#1688)

Commits

The new version differs by 17 commits.

4cd4a3b Bump version (v0.21.0) (#2690)
d59984f [docs] Add an announcement blog post for v0.21.0 (#2663)
1e38a58 fix wrong 'hasScroll' result for some IE specific case (part of #2511) (#2683)
6f20c41 Add two bugs to the changelog
684f4a7 Bump version (v0.21.0-alpha.1) (#2679)
8c8c403 Update CHANGELOG.md
3177a9a [docs] Changelog for v0.21.0 (#2656)
7b9ea07 Replace a long tweet with a shorter one (#2669)
17f869c Correct docs according to #2555 (#2657)
66a1127 [docs] address Lena's remark about screenshot path patterns (#2662)
2475642 [docs] Apply Dirk's corrections to the HTTPS topic (#2661)
d20708c Update createtestcafe.md
00f1d5c Fix client tests in Safari (#2652)
03fa1d0 [docs] describes -dev option (#2637)
7edc60e [docs] corrections - screenshotpathpattern (#2645)

There are 17 commits in total.

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper bot :palm_tree:

greenkeeper[bot] commented 6 years ago

zhenyulin / ultimate-hot-boilerplate