-
Notifications
You must be signed in to change notification settings - Fork 3
chore(deps): update monorepo:testcafe #127
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
base: master
Are you sure you want to change the base?
Conversation
b42295f
to
2c9f6c4
Compare
Codecov Report
@@ Coverage Diff @@
## master #127 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 9 9
Lines 30 30
Branches 1 1
=========================================
Hits 30 30 Continue to review full report at Codecov.
|
2c9f6c4
to
c889823
Compare
c889823
to
891b38c
Compare
891b38c
to
f19bb4b
Compare
Codecov ReportBase: 100.00% // Head: 100.00% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## master #127 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 9 9
Lines 30 30
Branches 1 1
=========================================
Hits 30 30 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
846ec07
to
0c789d5
Compare
0c789d5
to
fde4222
Compare
fde4222
to
ee5e622
Compare
ee5e622
to
03ea103
Compare
03ea103
to
82804f2
Compare
82804f2
to
d4f9f36
Compare
d4f9f36
to
f0d9363
Compare
f0d9363
to
babd6e1
Compare
babd6e1
to
7d355cf
Compare
7d355cf
to
cd89473
Compare
This PR contains the following updates:
4.3.1
->4.4.1
1.12.0
->1.20.1
Release Notes
testing-library/testcafe-testing-library (@testing-library/testcafe)
v4.4.1
Compare Source
Bug Fixes
Reverts
v4.4.0
Compare Source
Features
dependabot.yml
(#274) (551f130)DevExpress/testcafe (testcafe)
v1.20.1
Compare Source
Bug Fixes
fixture
andtest
definitions (PR #7187).v1.20.0
Compare Source
TestCafe v1.20.0 includes two major capabilities: an API testing toolkit and the ability to set a global test page URL. Additionally, TestCafe 1.20.0 introduces experimental support for Chrome User Flow Replays, as well as a number of under-the-hood improvements.
API Testing
TestCafe v1.20.0 includes a comprehensive set of server-side API testing tools. You can add dedicated API tests to your test suite, or include API testing methods in existing functional tests.
The new Request test action executes an HTTP request and returns the server's response.
Read the API Testing Guide for a full overview of the framework's API testing capabilities.
Global starting URL
You can now define a single starting URL for all the tests in your test suite.
Declare the
baseUrl
in one of the following three ways:Once you define a
baseUrl
, you can omit fixture and test URLs entirely, or define them relative to yourbaseUrl
:Experimental: Chrome User Flow Replays
TestCafe v1.20.0 introduces experimental, limited support for Google Chrome user flow recordings.
Record page actions in Google Chrome and export the recording as a JSON file. TestCafe will play the recording back just like it would a generate a test report
Read the User Flow Recordings guide to learn more.
Coming in TestCafe 2.0: TypeScript 4
The next version of TestCafe will adopt TypeScript 4 and lose compatibility with TypeScript 3.X.
To indicate the breaking change, we will increment the framework's major version number - from 1 to 2.
TestCafe 2.0 will be released later this month.
Improvements
Better Google Chrome video capture
TestCafe v1.20.0 uses the Screen Capture API to record videos of Google Chrome test runs. This results in a significantly better test recording framerate and image quality.
Bug Fixes
When the
t.typeText
action raises an error, TestCafe mistakenly awaits the target element for the second time (#6623)Concurrent test runs do not always generate concurrent test run reports (#7062)
TestCafe doesn't properly handle errors raised inside the
requestMock
function (#6703)The default terminal viewport width is too low for non-tty terminals (Issue #5919, PR #6930 by @PayBas)
TestCafe cannot switch to an invisible iframe (#4558)
Update incorrect TypeScript definitions (PR #7069 by @karolnowinsky)
Some SVGs don't meet the visibility criteria (#6998)
v1.19.0
Compare Source
TestCafe v1.19.0 introduces three major capabilities: a Cookie Management API, suite-wide test hooks, and suite-wide request hooks.
New Capabilities
Cookie Management
Previous versions of TestCafe lacked dedicated cookie management methods. Users had to write custom client functions to add and remove cookies. This technique was complicated and, at times, limiting. Some cookie manipulation actions --- such as HTTP-only cookie management --- were very hard to integrate into the test suite.
The latest version of the framework includes a proper set of cookie management tools that can handle a wide variety of tasks. Learn more about the new methods in our documentation: deleteCookies, getCookies, setCookies.
Global Test Hooks
Many TestCafe users employ test hooks --- functions that run before and after tests and fixtures. In TestCafe v1.19.0 and higher, you can attach hooks to test runs, as well as apply test hooks to your entire suite. This capability requires the use of a JavaScript configuration file.
Learn more about hooks from our newly updated hook guide.
Global Request Hooks
Request hooks are functions that intercept HTTP requests and mock HTTP responses. Earlier versions of TestCafe let you attach request hooks to one test or fixture at a time. You can now define global request hooks and attach them to multiple tests or fixtures in your suite.
Read the Request Hooks guide to learn more.
Bug Fixes
TestCafe ignores CLI browser arguments when they conflict with the configuration file (#6618)
The outdated
moment.js
dependency contains a critical vulnerability (PR #6996 by @vergilfromadyen)TestCafe proxy doesn't always serve cookies with the
secure
attribute (testcafe-hammerhead/#2715)v1.18.6
Compare Source
Bug Fixes
Faulty processing of client-side option chains leads to test execution errors (testcafe-hammerhead/#2714)
Poor Brotli compression performance (testcafe-hammerhead/#2743)
User Roles break when navigating to a new URL in a new window (PR testcafe-hammerhead/#2754)
The t.maximizeWindow method doesn't maximise browser windows on macOS (testcafe-browser-tools/#222)
v1.18.5
Compare Source
Bug Fixes
The t.scrollIntoView method causes the "Element is not visible" error when the target's
overflow
property ishidden
(#6601)TestCafe triggers click events for label elements even when the input is disabled (#6949)
TestCafe hangs when you change the active window between two consecutive assertions (#6037)
TestCafe cannot take screenshots when using the LambdaTest browser provider (#6887)
Pages that target a missing
<iframe>
(testcafe-hammerhead/#2178 element with theElement.focus
method yield a ""TypeError: window.location.toString is not a function" error.TestCafe causes errors when it encounters XMLHTTPRequest calls that fetch resources from
blob:
URLs (testcafe-hammerhead/#2634)HTMLElement.removeAttributeNode
method calls yield unjustified exceptions (PR testcafe-hammerhead/#2742 by @TrevorKarjanis)v1.18.4
Compare Source
Bug Fixes
TestCafe does not display reporter output during initialization (#6842)
TestCafe uses outdated automation scripts after cache expiration (testcafe-hammerhead/#2738, PR by @rr13k)
The
Node.append
method causes theIllegal invocation
error (PR testcafe-hammerhead/#2730 by @danieltroger)Scripts in SVG documents cause the
Illegal invocation
error (testcafe-hammerhead/#2735)v1.18.3
Compare Source
Bug Fixes
nanoid
package is vulnerable to CVE-2021-23566 (#6826)Selector.visibility
property does not depend on the parent elements' visibility (#3495)v1.18.2
Compare Source
Bug Fixes
<select>
elements (#5616)v1.18.1
Compare Source
macOS Bug Fix
TestCafe fails to launch Safari after the v1.18.0 update.
v1.18.0
Compare Source
TestCafe v1.18.0 includes a new experimental Selector debugging capability, important improvements for macOS users and a number of routine bug fixes.
If you run TestCafe on macOS, follow the Upgrade Guide to make sure your upgrade goes smoothly.
New Debugging Capabilities (Experimental)
If you launch TestCafe with the
--experimental-debug
flag, you can debug Selectors and Client Functions in the Watch panel of a Node.js debugger.macOS improvements
TestCafe Browser Tools on Apple Silicon
The TestCafe Browser Tools package is a communication layer that automates browsers on behalf of TestCafe. Both the TestCafe framework and TestCafe Studio include the TestCafe Browser Tools binary.
Earlier versions of TestCafe Browser Tools were optimized for the x86-64 architecture. Apple Silicon Macs ran those binaries through the Rosetta 2 translation layer. Rosetta 2 took up additional space and prevented TestCafe from taking full advantage of the processor.
TestCafe v1.18.0 includes a Universal TestCafe Browser Tools binary that runs natively on both x64 Macs and Apple Silicon Macs.
Follow the Upgrade Instructions to make sure your version of TestCafe Browser Tools is up to date.
TestCafe Browser Tools macOS Permission Fix
The TestCafe Browser Tools binary requires special privileges to automate browsers and take screenshots. Security improvements in recent versions of macOS made these privileges harder to obtain.
Prior to TestCafe v1.18.0, each installation of TestCafe and TestCafe Studio included a TestCafe Browser Tools binary. macOS users with multiple sets of TestCafe Browser Tools had to go through a lengthy process to obtain the necessary permissions.
TestCafe v1.18.0 and TestCafe Studio v1.7 address this issue. Beginning with this version, all TestCafe installations share a single TestCafe Browser Tools binary. TestCafe stores this binary in the user's Home directory, inside the hidden
~/.testcafe-browser-tools
folder.Follow the Upgrade Instructions to reset TestCafe Browser Tools' permissions and enable the new binary.
Bug Fixes
TypeError: Invalid value used as weak map key.
error (#6563)"Uncaught object "[object Object]"
(Issue #6624. Discovered by @danieltroger, PR by @rob4629.)v1.17.1
Compare Source
Bug Fixes
v1.17.0
Compare Source
Enhancements
Global Test and Fixture Hooks
You can now specify global test and fixture hooks. TestCafe attaches these hooks to every test / fixture in the test suite.
Execution Timeouts
You can now specify custom timeouts for tests and test runs. If a test/test run is idle or unresponsive for the specified length of time, TestCafe terminates it. Specify these timeouts in the configuration file or from the command line.
Command line interface
Configuration file
Bug Fixes
v1.16.1
Compare Source
Bug Fixes
v1.16.0
Compare Source
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: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 thetestcafe
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:Reference this variable in your test:
Other enhancements
embedding-utils
API method that retrieves information about skipped tests (PR by @flora8984461).Runner.filter
function supports asynchronous arguments (PR by @eignatyev).test
andfixture
objects directly from thetestcafe
module (PR #6338).Bug Fixes
v1.15.3
Compare Source
Bug Fixes
v1.15.2
Compare Source
Bug Fixes
tab
action if a page contains a cross-domain iframe (#6405).v1.15.1
Compare Source
Bug Fixes
Element.getAttribute
method returns an incorrect value (#5984).await
keyword before the assertion statement (#4613).v1.15.0
Compare Source
Enhancements
Dispatch DOM events (PR #6103)
The
t.dispatchEvent
method lets you interact with the page in ways that TestCafe does not support out of the box. To implement an unsupported user action, break it down into discrete DOM events, and use thet.dispatchEvent
method to fire them.The following example fires a
touchstart
action on an element with the 'button' id:Read the Custom Actions Guide for more information on DOM events and event constructors.
Quarantine mode customization (PR #6073 by @rob4629)
New settings are available in quarantine mode. Quarantine mode repeats failing tests to help users get conclusive test results in sub-optimal conditions. TestCafe v1.15 adds two variables -
successThreshold
andattemptLimit
- that allow you specify when TestCafe must stop.The
attemptLimit
variable determines the maximum possible number of test attempts.The
successThreshold
variable determines the number of successful attempts necessary for the test to pass.Password obfuscation (#6014)
TestCafe reporters no longer receive the contents of
password
input fields, unless you explicitly specify otherwise. This improves security for users that store their test results online.Support for non-HTML documents (#1471)
TestCafe now has the capability to proxy non-HTML documents such as XML and text files. Tests no longer hang upon redirection to a non-HTML address.
Bug Fixes
Navigator.prototype
requests (PR testcafe-hammerhead/#2643 by @michaelficarra).WorkerGlobalScope.importScripts()
arguments (testcafe-hammerhead/#2521).download
attributes cause TestCafe to hang (#6132).v1.14.2
Compare Source
v1.14.1
Compare Source
v1.14.0
Compare Source
v1.13.0
Compare Source
This release adds support for custom paths to the configuration file, support for Microsoft Edge on Linux systems, and multiple bugfixes.
Enhancements
⚙️ Specify Custom Path to the TestCafe Configuration File (PR #6035 by @Chris-Greaves)
TestCafe now allows you to specify a custom configuration file path.
To set this path, use one of the following options:
Add Support for Microsoft Edge on Linux (PR testcafe-browser-tools/#210 by @dcsaszar)
If you follow the Microsoft Edge Insider Channels for Linux and have Microsoft Edge installed on your Linux machine, you can now launch TestCafe tests in this browser.
⚙️ Deprecated the
t.setPageLoadTimeout
method (PR #5979)Starting with v1.13.0, the t.setPageLoadTimeout method is deprecated. To set the page load timeout, use the new test.timeouts method.
You can also use
test.timeouts
to set the pageRequestTimeout and ajaxRequestTimeout.Bug Fixes
hover
event on aradio
element (#5916)currentScope
calculation inside aWindow.postMessage
call (testcafe-hammerhead/#2524)RequestLogger
now shows a correct protocol for WebSocket requests (testcafe-hammerhead/#2591)No tests to run
error occurs in Live mode (#4257)documentElement.transform.translate
call moved the TestCafe UI in the browser window (#5606)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.