Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade testcafe from 1.15.2 to 1.17.0 #1626

Closed

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade testcafe from 1.15.2 to 1.17.0.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 9 versions ahead of your current version.
  • The recommended version was released a month ago, on 2021-11-02.
Release notes
Package name: testcafe
  • 1.17.0 - 2021-11-02

    What’s Changed

  • 1.17.0-rc.1 - 2021-10-27

    What’s Changed

  • 1.16.1 - 2021-10-05

    What’s Changed

  • 1.16.1-alpha.1 - 2021-10-04
    Read more
  • 1.16.0 - 2021-09-08

    v1.16.0 (2021-09-08)

    Enhancements

    Support for JavaScript configuration files

    You can now store TestCafe settings in a js file. Configuration properties in JavaScript files can reference JavaScript methods, functions and variables, which makes it easy to create dynamic configuration files.

    Just export the JSON name/value pairs in the file:

    module.exports = {
        skipJsErrors: true,
        hostname: "localhost",
        // other settings
    }

    Support for custom user variables in the configuration file

    TestCafe v1.16.0 and later supports configuration files with variable declarations. Users can reference variables from a configuration file in the tests that utilize that configuration file. To enable access to configuration file variables, import the userVariables object from the testcafe module at the beginning of the test script.

    This capability can come in handy if there's a single piece of data you want to use in multiple tests — for example, the website's URL. That way, if your website moves to a new domain name, you don't have to change your tests one by one.

    If you previously used environment variables to achieve the same goal, you might prefer the new method — it significantly simplifies the setup process, and allows you to commit the data to a version control system.

    Define your custom variables with the userVariables JSON object:

    {
      "userVariables": {
        "url": "http://devexpress.github.io/testcafe/example",
      }
    }

    Reference this variable in your test:

    import { userVariables } from 'testcafe';

    fixture Test user variables
    .page(userVariables.url);

    test('Type text', async t => {
    await t
    .typeText('#developer-name', 'John Smith')
    .click('#submit-button');
    });

    Other enhancements

    • New option that disables thumbnail generation for test screenshots (PR by @ taki-fw).
    • New embedding-utils API method that retrieves information about skipped tests (PR by @ flora8984461).
    • The Runner.filter function supports asynchronous arguments (PR by @ eignatyev).
    • You can import the test and fixture objects directly from the testcafe module (PR #6338).

    Bug Fixes

    • TestCafe does not keep track of file changes in live mode (#6481).
  • 1.16.0-rc.2 - 2021-09-02

    What’s Changed

  • 1.16.0-rc.1 - 2021-08-30
    Read more
  • 1.15.3 - 2021-08-19

    What’s Changed

  • 1.15.3-rc.1 - 2021-08-18
    Read more
  • 1.15.2 - 2021-08-11

    What’s Changed

from testcafe GitHub release notes
Commit messages
Package name: testcafe
  • 08833c1 release: v1.17.0 (#6666)
  • 902a4f3 Update changelog v1.17.0 (#6663)
  • 19dbe02 release: v1.17.0-rc.1 (#6650)
  • 3bef93e reporter API for matching test warnings and actions (#6630)
  • 0e9dc66 feat: added execution timeout (#6441)
  • 0e46a49 feat: added the possibility to assign global before/after for fixture/test (#6487)
  • 6737f0a Support live mode (#6638)
  • cb25b88 fix Should not break execution chain on using "t.debug" action (GH-6622) (#6636)
  • 79811ac close child window if it was opened for file downloading (closes #6242) (#6573)
  • 1af179b fix hammerhead tests (#6635)
  • 41edf66 update legacy-api (#6627)
  • e4aa752 Shared action executor (#6611)
  • 8d9c33f Update stale.yml
  • 3e225b1 fix: fix issue with accessing to some globals on client side (produced by the 'esm' module) (#6609)
  • c0fa15e fix: added rethrow an error of the Role in each test (#6587)
  • 36d9ff1 Update stale.yml
  • c941bd8 chore: notify customers about Selectors error in debug mode (#6598)
  • 5bd5ca7 Update stale.yml
  • d063447 fix selector timeout in debug mode (#6585)
  • 8d6d953 Update stale.yml
  • 1ad59b9 release: v1.16.1 (#6589)
  • da531e1 release: added the v1.16.1 changelog (#6588)
  • 9f1b142 release: bumped version, added missing @ babel/plugin-proposal-private-methods package (#6586)
  • c1bd426 feat: added the new 'reportWarnings' method for reporter (#6531)

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@coveralls
Copy link

coveralls commented Nov 30, 2021

Coverage Status

Coverage remained the same at 61.288% when pulling 8f25a59 on snyk-upgrade-0ac46766d091148daa2b731fd0d0daec into 80091b3 on master.

@tmeyer2115 tmeyer2115 closed this Nov 30, 2021
@jonhyler-yext jonhyler-yext reopened this Dec 1, 2021
@tmeyer2115 tmeyer2115 closed this Dec 10, 2021
@oshi97 oshi97 deleted the snyk-upgrade-0ac46766d091148daa2b731fd0d0daec branch March 15, 2022 21:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants