search

DevExpress / testcafe-selector-generator

MIT License
0 stars 2 forks source link

chore(deps): bump tough-cookie, qunit-harness, testcafe and testcafe-hammerhead #22

Open dependabot[bot] opened 7 months ago

dependabot[bot] commented 7 months ago

Bumps tough-cookie to 4.1.3 and updates ancestor dependencies tough-cookie, qunit-harness, testcafe and testcafe-hammerhead. These dependencies need to be updated together.

Updates tough-cookie from 2.4.3 to 4.1.3

Release notes

Sourced from tough-cookie's releases.

4.1.3

Security fix for Prototype Pollution discovery in #282. This is a minor release, although output from the inspect utility is affected by this change, we felt this change was important enough to be pushed into the next patch.

4.1.2 -- Patch and Bugfix Release

What's Changed

Full Changelog: https://github.com/salesforce/tough-cookie/compare/v4.1.1...v4.1.2

4.1.1

Patch Release

What's Changed

Full Changelog: https://github.com/salesforce/tough-cookie/compare/v4.1.0...v4.1.1

4.1.0

v4.1.0

Minor release, focused mainly on resolving reported issues and some minor feature work.

What's Changed

... (truncated)

Commits
  • 4ff4d29 4.1.3 release preparation, update the package and lib/version to 4.1.3. (#284)
  • 12d4747 Prevent prototype pollution in cookie memstore (#283)
  • f06b72d Fix documentation for store.findCookies, missing allowSpecialUseDomain proper...
  • b1a8898 fix: allow set cookies with localhost (#253)
  • ec70796 4.1.1 Patch -- allow special use domains by default (#250)
  • d4ac580 fix: allow special use domains by default (#249)
  • 79c2f7d 4.1.0 release to NPM (#245)
  • 4fafc17 Prepare tough-cookie 4.1 for publishing (updated GitHub actions, move Dockerf...
  • aa4396d fix: distinguish between no samesite and samesite=none (#240)
  • b8d7511 Modernize README (#234)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by awaterma, a new releaser for tough-cookie since your current version.


Updates qunit-harness from 1.3.12 to 1.3.14

Release notes

Sourced from qunit-harness's releases.

v1.3.14

What's Changed

Full Changelog: https://github.com/AlexanderMoskovkin/qunit-harness/compare/v1.3.13...v1.3.14

v1.3.13

No release notes provided.

Commits


Updates testcafe from 2.6.2 to 3.5.0

Release notes

Sourced from testcafe's releases.

v3.5.0 (2023-12-28)

TestCafe v3.5.0 includes multiple enhancements and bug fixes. Pass Selector queries to the Visual Selector Debugger, explore new ways to specify screenshot path patterns, and use a new experimental flag to run multi-window tests with native automation!

meta-readmore

Pass Selector queries to the Visual Selector Debugger

When you pass a Selector query to the https://github.com/DevExpress/testcafe/blob/HEAD[https://github.com/DevExpress/testcafe/blob/HEADthttps://github.com/DevExpress/testcafe/blob/HEAD.https://github.com/DevExpress/testcafe/blob/HEADdhttps://github.com/DevExpress/testcafe/blob/HEADehttps://github.com/DevExpress/testcafe/blob/HEADbhttps://github.com/DevExpress/testcafe/blob/HEADuhttps://github.com/DevExpress/testcafe/blob/HEADghttps://github.com/DevExpress/testcafe/blob/HEAD(https://github.com/DevExpress/testcafe/blob/HEAD)https://github.com/DevExpress/testcafe/blob/HEAD]https://github.com/DevExpress/testcafe/blob/HEAD(https://github.com/DevExpress/testcafe/blob/HEADxhttps://github.com/DevExpress/testcafe/blob/HEADrhttps://github.com/DevExpress/testcafe/blob/HEADehttps://github.com/DevExpress/testcafe/blob/HEADfhttps://github.com/DevExpress/testcafe/blob/HEAD:https://github.com/DevExpress/testcafe/blob/HEAD4https://github.com/DevExpress/testcafe/blob/HEAD0https://github.com/DevExpress/testcafe/blob/HEAD2https://github.com/DevExpress/testcafe/blob/HEAD7https://github.com/DevExpress/testcafe/blob/HEAD0https://github.com/DevExpress/testcafe/blob/HEAD7https://github.com/DevExpress/testcafe/blob/HEAD)https://github.com/DevExpress/testcafe/blob/HEAD method, TestCafe uses the query to populate the input field of the Visual Selector Debugger. The debugger highlights page elements that match the query.

t.debug(Selector('#header'));

Use a custom path pattern for screenshots of failed tests

The pathPatternOnFails screenshot option allows TestCafe users to define a separate set of naming rules for screenshots taken on test failure. You can store these screenshots in a different folder, or add a common, recognizable element to their filenames. You can use this option on its own, or in conjunction with the pathPattern property.

{
    "screenshots": {
        "pathPatternOnFails": "${DATE}_${TIME}/failedTests/test-${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}.png"
    }
}

Specify a path pattern for individual screenshots

Use the pathPattern option of the t.takeScreenshot action to specify a custom naming pattern for an individual screenshot:

t.takeScreenshot({
    pathPattern: "${DATE}_${TIME}/checkout-screenshot.png",
    fullPage: true
})

(Experimental) Run multi-window tests with native automation

TestCafe v2.5.0 was the first version of TestCafe to include native automation --- the capability to automate Chromium-based browsers with the native Chrome Debugging Protocol. This approach offers greater test stability and speed, but has a fair share of limitations. One of them is its incompatibility with multi-window tests.

TestCafe v3.5.0 offers an experimental solution for this issue --- the --experimental-multiple-windows CLI flag. If you enable this flag, you can run multi-window tests with the native automation engine.

The --experimental-multiple-windows mode does not support tests that include the following:

  • Pop-up windows that launch file downloads.
  • Browser window resizing.
  • Screenshots.
  • Video recording.

... (truncated)

Changelog

Sourced from testcafe's changelog.

v3.5.0 (2023-12-26)

TestCafe v3.5.0 includes multiple enhancements and bug fixes. Pass Selector queries to the Visual Selector Debugger, explore new ways to specify screenshot path patterns, and use a new experimental flag to run multi-window tests with native automation!

meta-readmore

Pass Selector queries to the Visual Selector Debugger

When you pass a Selector query to the https://github.com/DevExpress/testcafe/blob/master[https://github.com/DevExpress/testcafe/blob/masterthttps://github.com/DevExpress/testcafe/blob/master.https://github.com/DevExpress/testcafe/blob/masterdhttps://github.com/DevExpress/testcafe/blob/masterehttps://github.com/DevExpress/testcafe/blob/masterbhttps://github.com/DevExpress/testcafe/blob/masteruhttps://github.com/DevExpress/testcafe/blob/masterghttps://github.com/DevExpress/testcafe/blob/master(https://github.com/DevExpress/testcafe/blob/master)https://github.com/DevExpress/testcafe/blob/master]https://github.com/DevExpress/testcafe/blob/master(https://github.com/DevExpress/testcafe/blob/masterxhttps://github.com/DevExpress/testcafe/blob/masterrhttps://github.com/DevExpress/testcafe/blob/masterehttps://github.com/DevExpress/testcafe/blob/masterfhttps://github.com/DevExpress/testcafe/blob/master:https://github.com/DevExpress/testcafe/blob/master4https://github.com/DevExpress/testcafe/blob/master0https://github.com/DevExpress/testcafe/blob/master2https://github.com/DevExpress/testcafe/blob/master7https://github.com/DevExpress/testcafe/blob/master0https://github.com/DevExpress/testcafe/blob/master7https://github.com/DevExpress/testcafe/blob/master)https://github.com/DevExpress/testcafe/blob/master method, TestCafe uses the query to populate the input field of the Visual Selector Debugger. The debugger highlights page elements that match the query.

t.debug(Selector('#header'));

[!Video https://www.screencast.com/users/testcafe/folders/Default/media/4274d757-f7a4-4982-add4-43bb0ba35cff/embed]

Use a custom path pattern for screenshots of failed tests

The pathPatternOnFails screenshot option allows TestCafe users to define a separate set of naming rules for screenshots taken on test failure. You can store these screenshots in a different folder, or add a common, recognizable element to their filenames. You can use this option on its own, or in conjunction with the pathPattern property.

{
    "screenshots": {
        "pathPatternOnFails": "${DATE}_${TIME}/failedTests/test-${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}.png"
    }
}

Specify a path pattern for individual screenshots

Use the pathPattern option of the t.takeScreenshot action to specify a custom naming pattern for an individual screenshot:

t.takeScreenshot({
    pathPattern: "${DATE}_${TIME}/checkout-screenshot.png",
    fullPage: true
})

(Experimental) Run multi-window tests with native automation

TestCafe v2.5.0 was the first version of TestCafe to include native automation --- the capability to automate Chromium-based browsers with the native Chrome Debugging Protocol. This approach offers greater test stability and speed, but has a fair share of limitations. One of them is its incompatibility with multi-window tests.

TestCafe v3.5.0 offers an experimental solution for this issue --- the --experimental-multiple-windows CLI flag. If you enable this flag, you can run multi-window tests with the native automation engine.

The --experimental-multiple-windows mode does not support tests that include the following:

  • Pop-up windows that launch file downloads.
  • Browser window resizing.
  • Screenshots.

... (truncated)

Commits
  • 5cef9ac release: v3.5.0 (#8110)
  • 1ae1198 release: v3.5.0-rc.1 (#8107)
  • 51ad3bc feat: added pathPattern parameter to takeScreenshot method (#8093)
  • c782239 add missing multiple-windows-na task (#8105)
  • 61d6b4b feat: debug with selector option added (#8066)
  • 51b54c7 feat: Added path-pattern-on-fails for screenshots (closes #7014) (#8055)
  • 640cf6b feat: experimental multiple windows in native automation (#8080)
  • c4d1c49 build: Set @​babel/plugin-transform-runtime to a 7.23.3 version (#8103)
  • 20b6159 fix: In concurrent test run fixed awaiting of fixture before hook (#8097)
  • 6cab394 build(deps): bump @​adobe/css-tools from 4.3.1 to 4.3.2 (#8096)
  • Additional commits viewable in compare view


Updates testcafe-hammerhead from 28.4.2 to 31.7.1

Release notes

Sourced from testcafe-hammerhead's releases.

v31.7.1

What’s Changed

v31.7.0

What’s Changed

v31.6.4

What’s Changed

v31.6.3

What’s Changed

v31.6.1

What’s Changed

  • No changes

v31.6.0

What’s Changed

... (truncated)

Commits


You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/DevExpress/testcafe-selector-generator/network/alerts).

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.