zhenyulin / ultimate-hot-boilerplate

🚀 node-react universal app boilerplate with everything on hot reload, SSR, GraphQL, Flow included
MIT License
35 stars 4 forks source link

Update testcafe to the latest version 🚀 #49

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

Version 0.20.0 of testcafe was just published.

Dependency testcafe
Current Version 0.19.2
Type devDependency

The version 0.20.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.20.0

v0.20.0 (2018-5-15)

Request Hooks: Intercepting HTTP requests (#1341)

TestCafe now allows you to record HTTP request data or mock responses. You can also create a custom HTTP request hook to emulate authentications like Kerberos or Client Certificate Authentication.

See Intercepting HTTP Requests for more information.

Enhancements

⚙️ Specifying resources accessed by bypassing a proxy server (#1791)

TestCafe now allows you to bypass the proxy server when accessing specific resources.

To specify resources that require direct access, use the --proxy-bypass flag in the command line or the useProxy API method's parameters.

testcafe chrome my-tests/**/*.js --proxy proxy.corp.mycompany.com --proxy-bypass localhost:8080,internal-resource.corp.mycompany.com
runner.useProxy('172.0.10.10:8080', ['localhost:8080', 'internal-resource.corp.mycompany.com']);

⚙️ Specifying testing metadata (#2242)

TestCafe allows you to specify additional information for tests in the form of key-value metadata and use it in reports.

You can define metadata for a fixture or a test using the meta method:

fixture `My Fixture`
    .meta('fixtureID', 'f-0001')
    .meta({ author: 'John', creationDate: '05/03/2018' });
test
    .meta('testID', 't-0005')
    .meta({ severity: 'critical', testedAPIVersion: '1.0' })
    ('MyTest', async t => { /* ... */});

To include testing metadata to reports, use the custom reporter methods.

⚙️ Passing a regular promise to t.expect is deprecated now (#2207)

TestCafe now throws an error if you pass a regular promise to the assertion's expect method.

If you need to assert a regular promise, set the allowUnawaitedPromise option to true.

await t.expect(doSomethingAsync()).ok('check that a promise is returned', { allowUnawaitedPromise: true });

Bug Fixes

  • The session recovery bubble in Firefox is disabled (#2341)
  • TestCafe works properly if a body element has the pointer-events: none; css style rule (#2251)
  • Resizing Chrome in the emulation mode works correctly (#2154)
  • The location port is used for service messages (#2308)
  • A browser instance shuts down correctly on Unix systems (#2226)
  • An Integrity attribute is removed from script and link tags (testcafe-hammerhead/#235)
  • The event.preventDefault() method call changes the event.defaultPrevented property value (testcafe-hammerhead/#1588)
  • It is possible to set the meta element's content attribute (testcafe-hammerhead/#1586)
  • TestCafe no longer overrides attributes used in a non-standard way with null (testcafe-hammerhead/#1583)
  • The Change event fires correctly if the target.value changes (#2319)
  • MouseEvent.screenX and MouseEvent.screenY are added to the emulated events (#2325)
  • Cookies on localhost are processed correctly (testcafe-hammerhead/#1491)
  • Setting the // url for an image works correctly (#2312)
  • shadowUI internal elements are no longer processed (#2281)
  • typeInput event is raised correctly (#1956)
  • Selecting text in contenteditable elements works properly (#2301)
Commits

The new version differs by 41 commits.

  • 249739e Bump version (release); require Node.js>=6.0.0 (#2407)
  • e1464a6 [docs] Changelog v20 (#2385)
  • 59dcdbc [docs] Add v0.20.0 release notes (#2393)
  • b6031db filter parameter is required (#2405)
  • 3c97866 [docs] minor changes (#2401)
  • 4950171 [docs] Rename folder for request hooks, add a separate topic for RequestOptions (#2398)
  • 981d2dd Make TestCafe compatible with Node 10 (#2356)
  • ac06c5d [docs] Describe request hooks (#2309)
  • ec23eb2 0.20.0-alpha.4 (close #2384, close #2382, close #2070) (#2390)
  • 2d3c05a [docs] Update contribution (close #2297) (#2395)
  • 82667f7 update code_of_conduct (#2394)
  • 6975ca4 [docs] Assertion topic - Dirk corrections (#2376)
  • b1c8576 [docs] Docs Metadata (#2372)
  • 8e85a4d [docs] Describe bypassing the proxy (#2354)
  • b3bb34c TextInput event is not raised on typing (#closes 1956) (#2303)

There are 41 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:

coveralls commented 6 years ago

Coverage Status

Coverage remained the same at 100.0% when pulling dc694a017b049e4e72f6e65523fba15c4c7eedb4 on greenkeeper/testcafe-0.20.0 into 22835cc26b9af047c86f178b7d80b2dbf200141b on master.