JavaScript HTML TypeScript Other
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.github [docs] Added a contribution guide, code of conduct and issue template ( Oct 12, 2016
.md-lint [docs] Add the FAQ section (#1690) Aug 21, 2017
bin Handle SIGINT via async-exit-hook (closes #1378) (#1780) Sep 20, 2017
docker add --force flag for npm cache clean command (#2253) Mar 29, 2018
docs [docs] Replace vague phrasing (#2493) Jun 7, 2018
examples Fix example Feb 20, 2018
media [docs] Changelog v0.19 (#2126) Feb 21, 2018
src Use debug protocols for screenshots in Chrome and Firefox (#2492) Jun 7, 2018
test Use debug protocols for screenshots in Chrome and Firefox (#2492) Jun 7, 2018
ts-defs bump version (close #2095) (#2451) May 24, 2018
.dockerignore Add TS definitions to the Docker image (#2481) Jun 1, 2018
.editorconfig Start implementing build infrastructure Jun 25, 2015
.eslintignore Fix `ReferenceError: selector is not defined` if selector promise is … Aug 12, 2016
.eslintrc Update hammerhead (#2122) Feb 15, 2018
.gitattributes Fix EOL in TS files (#1748) Aug 31, 2017
.gitignore Implement usage of scopes in pool importing of browser providers. Fixes Apr 5, 2018
.publishrc 0.20.1 (#2443) May 22, 2018
.travis-docs.yml Try a newer version of Ruby Dec 5, 2017
.travis.yml Enable maximize for headless browsers; Add a flag for disable multipr… Jun 4, 2018
CHANGELOG.md [docs] Replace vague phrasing (#2493) Jun 7, 2018
CODE_OF_CONDUCT.md update code_of_conduct (#2394) May 11, 2018
CONTRIBUTING.md [docs] Remove forum links (#2442) May 22, 2018
Gulpfile.js Use debug protocols for screenshots in Chrome and Firefox (#2492) Jun 7, 2018
LICENSE Update year in license Jan 16, 2017
README.md [docs] Remove forum links (#2442) May 22, 2018
appveyor.yml Use debug protocols for screenshots in Chrome and Firefox (#2492) Jun 7, 2018
package.json Bump version (v0.20.3) (#2494) Jun 6, 2018

README.md

testcafe

Functional Windows desktop All Travis tasks (server, client, functional: mobile, macOS, Edge) NPM Version

A Node.js tool to automate end-to-end web testing.
Write tests in JS or TypeScript, run them and view results.

https://devexpress.github.io/testcafe


  • Works on all popular environments: TestCafe runs on Windows, MacOS, and Linux. It supports desktop, mobile, remote and cloud browsers (UI or headless).
  • 1 minute to set up: You do not need WebDriver or any other testing software. Install TestCafe with one command, and you are ready to test: npm install -g testcafe
  • Free and open source: TestCafe is free to use under the MIT license. Plugins provide custom reports, integration with other tools, launching tests from IDE, etc. You can use the plugins made by the GitHub community or make your own.

Install TestCafe and Run a Test

Running a sample test in Safari

Table of contents

Features

Stable tests and no manual timeouts
TestCafe automatically waits for page loads and XHRs before the test starts and after each action. It also features smart test actions and assertions that wait for page elements to appear. You can change the maximum wait time. If elements load faster, tests skip the timeout and continue.

Rapid test development tool
Changes in test code immediately restart the test, and you see the results instantly.
See how it works in the TestCafe Live repository.

Latest JS and TypeScript support
TestCafe supports the latest JavaScript features, including ES2017 (for example, async/await). You can also use TypeScript if you prefer a strongly typed language.

Detects JS errors in your code
TestCafe reports JS errors that it finds on the webpage. Tests automatically fail because of that. However, you can disable this.

Concurrent tests launch
TestCafe can open multiple instances of the same browser to run parallel tests which decreases test execution time.

PageObject pattern support
The TestCafe's Test API includes a high-level selector library, assertions, etc. You can combine them to implement readable tests with the PageObject pattern.

const macOSInput = Selector('.column').find('label').withText('MacOS').child('input');

Easy to include in a continuous integration system
You can run TestCafe from a console, and its reports can be viewed in a CI system's interface (TeamCity, Jenkins, Travis & etc.)

Getting Started

Installation

Ensure that Node.js (version 4 or newer) and npm are installed on your computer before running it:

npm install -g testcafe

Creating the Test

As an example, we are going to test the https://devexpress.github.io/testcafe/example page.

Create a .js or .ts file on your computer. Note that it needs to have a specific structure: tests must be organized into fixtures. You can paste the following code to see the test in action:

import { Selector } from 'testcafe'; // first import testcafe selectors

fixture `Getting Started`// declare the fixture
    .page `https://devexpress.github.io/testcafe/example`;  // specify the start page


//then create a test and place your code there
test('My first test', async t => {
    await t
        .typeText('#developer-name', 'John Smith')
        .click('#submit-button')

        // Use the assertion to check if the actual header text is equal to the expected one
        .expect(Selector('#article-header').innerText).eql('Thank you, John Smith!');
});

Running the Test

Call the following command in a command shell. Specify the target browser and file path.

testcafe chrome test1.js

TestCafe opens the browser and starts executing the test.

Important! Make sure to stay in the browser tab that is running tests. Do not minimize the browser window. Tests are not guaranteed to execute correctly in inactive tabs and minimized browser windows because they switch to a lower resource consumption mode.

Viewing the Results

TestCafe outputs the results into a command shell by default. See Reporters for more information. You can also use plugins to customize the reports.

Test Report

Read the Getting Started page for a more detailed guide.

Documentation

Go to our website for full documentation on TestCafe.

Community

Follow us on Twitter. We post TestCafe news and updates, several times a week.

Badge

Show everyone you are using TestCafe: Tested with TestCafe

To display this badge, add the following code to your repository readme:

<a href="https://github.com/DevExpress/testcafe">
    <img alt="Tested with TestCafe" src="https://img.shields.io/badge/tested%20with-TestCafe-2fa4cf.svg">
</a>

Contributing

Report bugs and request features on our issues page.
Ask questions and participate in discussions at the Support Center.
For more information on how to help us improve TestCafe, see the CONTRIBUTING.md.

You can use these plugin generators to create your own plugins:

If you want your plugin to be listed below, send us a note in a Github issue.

Plugins

TestCafe developers and community members made these plugins:

Thanks to BrowserStack

We are grateful to BrowserStack for providing the infrastructure that we use to test code in this repository.

BrowserStack Logo

License

Code released under the MIT license.

Creators

Developer Express Inc. (https://devexpress.com)