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.

Sign up for GitHub

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

Jump to bottom

Update dependency testcafe to v1 #33

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update dependency testcafe to v1 #33

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 9, 2019 •
edited
Loading

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
testcafe (source) ^0.23.0 -> ^1.18.4 age adoption passing confidence

Release Notes

DevExpress/testcafe

v1.18.4

Compare Source

Bug Fixes

v1.18.3

Compare Source

Bug Fixes
  • The nanoid package is vulnerable to CVE-2021-23566 (#​6826)
  • The Selector.visibility property does not depend on the parent elements' visibility (#​3495)

v1.18.2

Compare Source

Bug Fixes
  • Tests with client scripts yield the "Cannot read property 'tests' of null" error (#​6305)
  • TestCafe hangs after failing to initialize a Role (#​5278)
  • Testcafe falsely detects filter directives in the configuration file (#​6620)
  • Concurrent Chrome instances cannot reconnect to TestCafe after a restart (#​4554)
  • TestCafe hangs if a user enters an iframe and then switches to a different browser window (#​6085)
  • TestCafe opens incorrect URLs when you concurrently run multiple fixtures from the same test file (#​6041)
  • TestCafe expands disabled <select> elements (#​5616)
  • TestCafe does not load some cross-domain iframes (#​6633)
  • TestCafe incorrectly sets the Document.referrer property in Chrome 89 (#​6144)
  • Tests hang when the test page initiates a file download (#​5796)
  • Requests fail because TestCafe incorrectly handles dynamic content security policy (#​6057)
  • TestCafe triggers pointerdown event handlers twice (#​5891)
  • TestCafe cannot trigger click event handlers for Angular buttons with the "disabled" attribute (#​5240)

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
  • TestCafe immediately closes new windows (#​6680)
  • Tests fail with the TypeError: Invalid value used as weak map key. error (#​6563)
  • The latest version of the TestCafe Docker image cannot connect to Chrome and Chromium (#​6436)
  • TestCafe loses test error call stack and outputs the following message instead: "Uncaught object "[object Object]" (Issue #​6624. Discovered by @​danieltroger, PR by @​rob4629.)
  • Lack of definitions for two new timeout options results in TypeScript compilation errors (#​6713)
  • TypeScript filter functions erroneously require a Promise return value (#​6705)

v1.17.1

Compare Source

Bug Fixes
  • TestCafe incorrectly reads the 'reporter' configuration file option (#​6665, #​6594).
  • An error report displays multiple warnings when you debug a test in headless mode (#​6605).
  • The testcafe-hammerhead proxy fails to load a web page (testcafe-hammerhead/#​2708).

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.

module.exports = {
    hooks: {
        fixture: {
            before: async (ctx) => {
                // your code
            },
            after: async (ctx) => {
                // your code
            }
        },
        test: {
            before: async (t) => {
                // your code
            },
            after: async (t) => {
                // your code
            }
        }
    }
};
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

testcafe chrome my-tests --test-execution-timeout 180000
testcafe chrome my-tests --run-execution-timeout 180000

Configuration file

{
    "runExecutionTimeout": 180000,
    "testExecutionTimeout": 180000
}
Bug Fixes
  • TestCafe fails to continue the test after the user downloads a file. (#​6242).
  • The TestCafe proxy does not fire the "unpipe" event when necessary. This omission leads to the "This socket has been ended by the other party" error (#​6558).
  • TestCafe incorrectly handles rewritten uninitialized iframes (testcafe-hammerhead/#​2694, testcafe-hammerhead/#​2693).

v1.16.1

Compare Source

Bug Fixes
  • Incorrect handling of the beforeInput Firefox event (#​6504)
  • Incorrect handling of page styles leads to test failure in Safari 15 (#​6546)
  • Incorrect stylesheet filtering procedure leads to client-side errors in IE11 (#​6439)

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:

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).

v1.15.3

Compare Source

Bug Fixes

v1.15.2

Compare Source

Bug Fixes

v1.15.1

Compare Source

Bug Fixes
  • The Element.getAttribute method returns an incorrect value (#​5984).
  • TestCafe test fails when you forget to include the await keyword before the assertion statement (#​4613).
  • TestCafe fails to focus an element inside a shadow DOM (#​4988).
  • TestCafe fails to focus SVG elements (#​6262).
  • TestCafe raises the blur event when you focus a non-focusable element (#​6236).
  • TestCafe test hangs when you click a link within a cross-domain iframe (#​6331).
  • TestCafe loads the Babel compiler libraries multiple times (#​6310).
  • TestCafe incorrectly parses the meta refresh tags (#​2663)
  • TestCafe incorrectly processes iframe elements with the "srcdoc" attribute (#​2647).
  • TestCafe incorrectly specifies the Referer HTTP request header if you use the "navigateTo" action (#​2607).
  • An error related to the bug in Node.js occurs (#​2655).

v1.15.0

Compare Source

Enhancements
Dispatch DOM events (PR #​6103)
t.dispatchEvent(target, eventName[, options])

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 the t.dispatchEvent method to fire them.

Internet Explorer does not support event constructors. As such, TestCafe cannot dispatch DOM events in this browser.

The following example fires a touchstart action on an element with the 'button' id:

await t.dispatchEvent('#button', 'touchstart',  { eventConstructor: 'TouchEvent' });

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 and attemptLimit - 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.

testcafe chrome ./tests/ -q attemptLimit=5, successThreshold=2
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

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.

testcafe edge tests/test.js
⚙️ 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.

fixture`Setting Timeouts`
    .page`http://devexpress.github.io/testcafe/example`;

test
    .timeouts({
        pageLoadTimeout: 2000
    })
    ('My test', async t => {
        //test actions
    })

You can also use test.timeouts to set the pageRequestTimeout and ajaxRequestTimeout.

fixture`Setting Timeouts`
    .page`http://devexpress.github.io/testcafe/example`;

test
    .timeouts({
        pageLoadTimeout:    2000,
        pageRequestTimeout: 60000,
        ajaxRequestTimeout: 60000
    })
    ('My test', async t => {
        //test actions
    })
Bug Fixes
  • Fixed a bug where TestCafe would sometimes be unable to trigger a hover event on a radio element (#​5916)
  • Fixed a bug where TestCafe was unable to register a Service Worker due to the wrong currentScope calculation inside a Window.postMessage call (testcafe-hammerhead/#​2524)
  • RequestLogger now shows a correct protocol for WebSocket requests (testcafe-hammerhead/#​2591)
  • Test execution now pauses when the browser window is in the background (testcafe-browser-tools/#​158)
  • TestCafe now appends an extension to screenshot filenames (#​5103)
  • Fixed a bug where TestCafe would emit test action events after the end of a test run (#​5650)
  • TestCafe now closes if the No tests to run error occurs in Live mode (#​4257)
  • Fixed a freeze that happened when you run a test suite with skipped tests (#​4967)
  • Fixed an error where a documentElement.transform.translate call moved the TestCafe UI in the browser window (#​5606)
  • TestCafe now emits a warning if you pass an unawaited selector to an assertion (#​5554)
  • Fixed a crash that sometimes occurred in Chrome v85 and earlier on pages with scripts (PR testcafe-hammerhead/#​2590)

v1.12.0

Compare Source

Enhancements
⚙️ Server-Side Web Assets Caching (testcafe-hammerhead/#​863)

TestCafe's proxy server can now cache web assets (like images, scripts and videos). When TestCafe revisits a website, it loads assets from this cache to save time on repetetive network requests.

To enable server-side caching, use any of the following:

Initialize Request Hooks with Async Predicates

The following request hooks now support asynchronous predicate functions:

Example

const logger = RequestLogger(async request => {
    return await myAsyncFunction();
});
Bug Fixes
  • Fixed a bug in Multiple Windows mode where TestCafe was sometime unable to switch to the main browser window (#​5930)
  • Fixed the Illegal invocation error thrown by TestCafe when calling Storage.prototype methods on a StorageWrapper object (#​2526)

v1.11.0

Compare Source

Enhancements
⚙️ Set Request Timeouts (PR #​5692)

TestCafe now enables you to set request timeouts. If TestCafe receives no response within the specified period, it throws an error.

CLI

testcafe chrome my-tests --ajax-request-timeout 40000 --page-request-timeout 8000

Configuration file

{
    "pageRequestTimeout": 8000,
    "ajaxRequestTimeout": 40000
}

JavaScript API

These options are available in the runner.run Method.

const createTestCafe = require('testcafe');

const testcafe = await createTestCafe('localhost', 1337, 1338);

try {
    const runner = testcafe.createRunner();

    const failed = await runner.run({
        pageRequestTimeout: 8000,
        ajaxRequestTimeout: 40000
    });

    console.log('Tests failed: ' + failed);
}
finally {
    await testcafe.close();
}
⚙️ Set Browser Initialization Timeout (PR #​5720)

This release introduces an option to control browser initialization timeout. This timeout controls the time browsers have to connect to TestCafe before an error is thrown. You can control this timeout in one of the following ways:

testcafe chrome my-tests --browser-init-timeout 180000
{
    "browserInitTimeout": 180000
}
runner.run({ "browserInitTimeout": 180000 })

This setting sets an equal timeout for local and remote browsers.

Improved Unable To Establish Browser Connection Error Message (PR #​5720)

TestCafe raises this error when at least one local or remote browser was not able to connect. The error message now includes the number of browsers that have not established a connection.

TestCafe raises a warning if low system performance is causing the connectivity issue.

⚙️ An Option to Retry Requests for the Test Page (PR #​5738)

If a tested webpage was not served after the first request, TestCafe can now retry the request.

You can enable this functionality with a command line, API, or configuration file option:

  • the --retry-test-pages command line argument

    testcafe chrome test.js --retry-test-pages

  • the createTestCafe function parameter

    const createTestCafe = require('testcafe');

const testcafe = await createTestCafe('localhost', 1337, 1338, retryTestPages)

  • the retryTestPages configuration file property

    {
    "retryTestPages": true
}
Bug Fixes
Vulnerability Fix (PR #​5843, PR testcafe-hammerhead#​2531)

We have fixed a vulnerability found in the debug module we use for debugging.
The vulnerability was a ReDos Vulnerability Regression that affected all TestCafe users. TestCafe now uses [email protected], where the issue is fixed.

v1.10.1

Compare Source

Bug Fixes
  • Fixed an error thrown when TestCafe runs TypeScript tests (#​5808)
  • Implemented a Service Worker that allows TestCafe to re-try failed requests to the tested page. This improves test stability (#​5239)
  • Fixed an error thrown when you call the t.getBrowserConsoleMessages method (#​5600)

v1.10.0

Compare Source

Enhancements
Window Resize and Screenshot Support for Child Windows in Chrome (PR #​5661, PR #​5567)

You can now use the following actions in Google Chrome when you switch the test context to a child window:

New API to Specify Compiler Options (#​5519)

In previous versions, you used the following methods to specify TypeScript compiler options:

  • the --ts-config-path command line flag

    testcafe chrome my-tests --ts-config-path path/to/config.json

  • the runner.tsConfigPath method

    runner.tsConfigPath('path/to/config.json');

  • the tsConfigPath configuration file property

    {
    "tsConfigPath": "path/to/config.json"
}

In v1.10.0, we introduced a new easy-to-use API that allows you to specify the compiler options in the command line, API or TestCafe configuration file, without creating a separate JSON file. The new API is also designed to accept options for more compilers (for instance, Babel) in future releases.

The API consists of the following members:

  • the --compiler-options command line flag

    testcafe chrome my-tests --compiler-options typescript.experimentalDecorators=true

  • the runner.compilerOptions method

    runner.compilerOptions({
    typescript: {
        experimentalDecorators: true
    }
});

  • the compilerOptions configuration file property

    {
    "compilerOptions": {
        "typescript": {
            "experimentalDecorators": true
        }
    }
}

If you prefer to keep compiler settings in a configuration file, you can use the new API to specify the path to this file:

testcafe chrome my-tests --compiler-options typescript.configPath='path/to/config.json'

In v1.10.0, you can customize TypeScript compiler options only.

For more information, see TypeScript and CoffeeScript.

Added a Selector Method to Access Shadow DOM (PR #​5560 by @​mostlyfabulous)

This release introduces the selector.shadowRoot method that allows you to access and interact with the shadow DOM elements. This method returns a shadow DOM root hosted in the selector's matched element.

import { Selector } from 'testcafe'

fixture `Target Shadow DOM elements`
    .page('https://devexpress.github.io/testcafe/example')

test('Get text within shadow tree', async t => {
    const shadowRoot = Selector('div').withAttribute('id', 'shadow-host').shadowRoot();
    const paragraph  = shadowRoot.child('p');

    await t.expect(paragraph.textContent).eql('This paragraph is in the shadow tree');
});

Note that you should chain other selector methods to selector.shadowRoot to access elements in the shadow DOM. You cannot interact with the root element (an error occurs if you specify selector.shadowRoot as an action's target element).

Bug Fixes

v1.9.4

Compare Source

Bug Fixes

v1.9.3

Compare Source

Bug Fixes
  • Fixed the RequestMock type definitions to accept any type for the headers (#​5529)
  • TestCafe no longer displays a warning about missing await when you save a snapshot property to a variable but do not use it later in the test (#​5534)
  • Consecutive document.getElementsByTagName('body') calls now produce the correct results even if the first call was made before a document body was parsed entirely (#​5322)

v1.9.2

Compare Source

Bug Fixes
  • TestCafe's TypeScript definitions now allow null as an expected value in assertions (PR #​5456)
  • Added warnings displayed when a user tries to get a snapshot property value and misses await (PR #​5383, part of #​5087)
  • Tested app's standard output and error streams are forwarded to the TestCafe's debug log now (#​5423)
  • Tested apps no longer cause buffer overflow errors when they output too much data to standard streams (#​2857)
  • TestCafe now correctly waits for elements on tested pages that mock date functions (#​5447)
  • HTTP header overflow errors now occur less frequently due to the increased maximum header size. Enhanced the error message with troubleshooting instructions (testcafe-hammerhead/#​2356)
  • Added a descriptive message with troubleshooting instructions for the error thrown when the tested web server sends malformed or non-standard headers (testcafe-hammerhead/#​2188)
  • Fixed a CSRF error on tested pages that use the Request class (testcafe-hammerhead/#​2140)
  • t.hover now works correctly for tested pages built with the Styled Components framework (#​3830)
  • Fixed script processing that could cause unhandled exceptions on some pages (testcafe-hammerhead/#​2417)
  • Fixed the 'TypeError: r is not a function' uncaught exception on some pages with an <iframe> (testcafe-hammerhead/#​2392)

v1.9.1

Compare Source

Bug Fixes

v1.9.0

Compare Source

Enhancements
🌟 Multi Window Support (Beta)

TestCafe can now automate user actions in multiple windows. You can switch between open windows during the test. Make edits in one window and check that the other window's content changes dynamically to reflect these modifications.

Testing in multiple windows

When the main window opens a child window, TestCafe automatically switches to this new window and continues test actions there:

import { Selector } from 'testcafe';

fixture `Login page`
    .page('https://login.wrike.com/login/');

const googleButton = Selector('div.login-panel-footer__login-with > button');

test('Login via Google', async t => {
    await t
        .click(googleButton)
        .typeText('input[type=email]', 'This text will be entered inside the pop-up');
});

You can use the t.openWindow method to open a child window in test code:

import { Selector, ClientFunction } from 'testcafe';

fixture `Test page`
    .page('https://devexpress.github.io/testcafe/example/');

test('Open a new window', async t => {
    await t.openWindow('http://example.com');

    const url = await t.eval(() => document.documentURI);

    await t.expect(url).eql('http://example.com');
});

The t.switchToWindow method enables you to switch between open windows. You can use a window descriptor or a predicate to specify the window that should be activated:

fixture `Example page`
    .page('https://example.com');

test('Switch to a specific window', async t => {
    const initialWindow = await t.getCurrentWindow();
    const popUp1        = await t.openWindow('https://devexpress.com');
    const popUp2        = await t.openWindow('https://github.com');

    await t.switchToWindow(initialWindow);

    const url = t.eval(() => document.documentURI);

    await t.expect(url).eql('https://example.com/');

    await t
        .switchToWindow(w => w.url.host === 'github.com')
        .expect(url).eql('https://github.com');
});

The t.switchToParentWindow and t.switchToPreviousWindow methods allow you to switch back to the parent window or the previously active window.

The t.closeWindow method closes the current window when called without arguments, or the specified window if you pass a descriptor or predicate:

fixture `Example page`
    .page('http://www.example.com');

test('Close the current window', async t => {
    const window1 = await t.openWindow('http://devexpress.com');

    await t.closeWindow();

    const url = await t.eval(() => document.documentURI);

    await t.expect(url).eql('http://www.example.com/');
});

test('Close a specific window', async t => {
    const window1 = await t.openWindow('http://devexpress.com');

    await t.closeWindow(window1);
});
Detailed Diffs in Failed Assertions

Test run reports now show the differences between an assertion's actual and expected values:

A report showing differences between asserted values

TestCafe can display difference between values, arrays, objects, and even functions.

Bug Fixes
  • TestCafe now throws a descriptive error when it attempts to start the browser UI on Linux without the X11 server (4461)
  • Exception no longer thrown when you use remote browsers on Linux without X11 or run Windows browsers from WSL2 ([#​4742](https://togithub.com/D

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 4fcf589 to 73d0c1f Compare February 14, 2019 17:26
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 73d0c1f to 3238dd4 Compare February 28, 2019 17:34
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch 2 times, most recently from a52c77d to 1c09432 Compare April 10, 2019 13:33
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 1c09432 to f84582c Compare April 18, 2019 14:39
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from f84582c to 8fecbbd Compare May 7, 2019 11:41
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 8fecbbd to f58d334 Compare May 28, 2019 17:11
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from f58d334 to 84d626b Compare June 19, 2019 14:44
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 84d626b to 4adb4af Compare July 13, 2019 14:59
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 4adb4af to 864670a Compare August 10, 2019 08:54
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 864670a to 8bc13b4 Compare August 20, 2019 04:57
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 8bc13b4 to 441a71b Compare September 5, 2019 04:51
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 441a71b to 079beec Compare October 4, 2019 12:52
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 079beec to 6d95d06 Compare November 11, 2019 14:55
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 6d95d06 to fd954fe Compare December 14, 2019 22:52
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from fd954fe to da6e0b8 Compare December 22, 2019 06:57
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from da6e0b8 to 98b05b7 Compare January 18, 2020 23:59
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 98b05b7 to 29020cd Compare February 8, 2020 21:52
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 29020cd to 3294f2b Compare March 14, 2020 14:58
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 3294f2b to f65bcba Compare May 2, 2020 21:58
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from f65bcba to da51f61 Compare June 30, 2020 14:55
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from da51f61 to a603b3a Compare July 10, 2020 12:51
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from a603b3a to 0669a5e Compare August 26, 2020 00:58
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 0669a5e to b981a46 Compare October 28, 2020 08:00
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from b981a46 to 1ca99b4 Compare January 6, 2021 16:56
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from 1ca99b4 to c5da39d Compare April 26, 2021 16:55
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from c5da39d to d3b0fc6 Compare May 15, 2021 19:12
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from d3b0fc6 to c17add3 Compare October 18, 2021 19:27
@renovate renovate bot force-pushed the renovate/testcafe-1.x branch from c17add3 to 190bb22 Compare March 7, 2022 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@renovate-bot