Update dependency testcafe to ^0.23.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
testcafe (source)	^0.23.0 -> ^0.23.3

---

Release Notes

DevExpress/testcafe

v0.23.3

Compare Source

Bug Fixes

• Remote browsers now start after tests are compiled (#​3219) by @​link89
• The TestCafe Docker image now includes version tags (#​2315)
• Tests now fail with a meaningful error if no fixture is defined (#​2913)
• Tests now resume correctly after a long waiting (#​3070)
• TestCafe now throws a meaningful exception when taking screenshots in a browser that does not support it (#​2878)
• Events are now simulated in the correct order when focusing an element after another element was focused on the changed event (#​3098)
• The Invalid calling object exception is no longer thrown in IE11 (testcafe-hammerhead/#​1846)
• The JSON parse error is no longer thrown when sending an XHR request (testcafe-hammerhead/#​1839)
• Overridden functions now have the right prototype in an iframe without src (testcafe-hammerhead/#​1824)
• gulp-testcafe now correctly closes Chrome after tests are finished (testcafe-hammerhead/#​1826)
• Saving the window prototype to a property now works correctly (testcafe-hammerhead/#​1828)
• Hammerhead is now retained after document.close in Firefox (testcafe-hammerhead/#​1821)

v0.23.2

Compare Source

Bug Fixes

• TestCafe no longer posts internal messages to the browser console (#​3099)
• The TestCafe process no longer terminates before the report is written to a file (#​2502)

v0.23.1

Compare Source

Enhancements

⚙️ Select Tests and Fixtures to Run by Their Metadata (#​2527) by @​NickCis

You can now run only those tests or fixtures whose metadata contains a specific set of values. Use the --test-meta and --fixture-meta flags to specify these values.

testcafe chrome my-tests --test-meta device=mobile,env=production

testcafe chrome my-tests --fixture-meta subsystem=payments,type=regression

In the API, test and fixture metadata is now passed to the runner.filter method in the testMeta and fixtureMeta parameters. Use this metadata to build a logic that determines whether to run the current test.

runner.filter((testName, fixtureName, fixturePath, testMeta, fixtureMeta) => {
    return testMeta.mobile === 'true' &&
        fixtureMeta.env === 'staging';
});

⚙️ Run Dynamically Loaded Tests (#​2074)

You can now run tests imported from external libraries or generated dynamically even if the .js file does not contain any tests.

Previously, test files had to contain the fixture and test directives. You can now add the --disable-test-syntax-validation command line flag to bypass this check.

testcafe safari test.js --disable-test-syntax-validation

In the API, use the disableTestSyntaxValidation option.

runner.run({ disableTestSyntaxValidation: true })

Bug Fixes

• Touch events are now simulated with correct touch properties (touches, targetTouches, changedTouches) (#​2856)
• Google Chrome now closes correctly on macOS after tests are finished (#​2860)
• Internal attribute and node changes no longer trigger MutationObserver notifications (testcafe-hammerhead/#​1769)
• The ECONNABORTED error is no longer raised (testcafe-hammerhead/#​1744)
• Websites that use Location.ancestorOrigins are now proxied correctly (testcafe-hammerhead/#​1342)

---

Configuration

📅 Schedule: "before 3am on the first day of the month" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.