Skip to content
A node.js library for testing modern web applications
JavaScript TypeScript HTML
Branch: master
Clone or download

Latest commit

zabil Add window name paramter to the documentation (#1294)
Signed-off-by: Zabil Cheriya Maliackal <zabilcm@gmail.com>
Latest commit cb3f272 May 28, 2020

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update chromium to revision 756035 (#1195) Apr 16, 2020
.idea fix for #733 Aug 9, 2019
.vscode launching taiko with integratedTerminal Dec 11, 2019
bin #1241 Fix closeBrowser issues (#1258) May 18, 2020
docs Remove algolia options May 6, 2020
examples Add time field (#1172) Apr 9, 2020
lib Add window name paramter to the documentation (#1294) May 28, 2020
recorder Fix documentation for repl (#886) Oct 18, 2019
test hide value for taiko commands in repl May 25, 2020
types/taiko Fix incorrect return types in type declaration (#1287) May 25, 2020
.eslintrc Port test to ts (#1212) May 4, 2020
.gitignore Add algolia docsearch May 6, 2020
.npmignore Update taiko version to 0.8.0 for further development May 29, 2019
.prettierignore prettier formatting moved from function-test to root repo and added l… Aug 27, 2019
.prettierrc changed prettier linewidth to 100 for better readability and fix eslint Jan 13, 2020
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md May 14, 2019
CONTRIBUTING.md Remove CLA May 21, 2020
LICENSE Basic setup for the repo Oct 27, 2017
README.md added experimental typescript support (#1125) Apr 20, 2020
_redirects Change references to new domain (#1068) Jan 31, 2020
netlify.toml Set up a redirect to list of devices (#1204) Apr 20, 2020
package-lock.json Bump @babel/parser from 7.10.0 to 7.10.1 May 28, 2020
package.json Reference type declarations (#1278) May 22, 2020
updateChromium.js Auto update chromium to stable version Apr 6, 2020

README.md

Taiko

A Node.js library for testing modern web applications

Actions Status License MIT npm version dependencies Status devDependencies Status contributions welcome Contributor Covenant

Taiko REPL

What’s Taiko?

Taiko is a free and open source browser automation tool built by the team behind Gauge from ThoughtWorks. Taiko is a Node.js library with a clear and concise API to automate Chromium based browsers(Chrome, Microsoft Edge, Opera). Tests written in Taiko are highly readable and maintainable.

With Taiko it’s easy to

  • Get Started
  • Record/Write/Run tests

Taiko’s smart selectors make tests reliable by adapting to changes in the structure of your web application. With Taiko there’s no need for id/css/xpath selectors or adding explicit waits (for XHR requests) in test scripts.

Features

Taiko is built ground up to test modern web applications. Here’s a list of a few unique features that sets it apart from other browser automation tools.

  • Easy Installation
  • Interactive Recorder
  • Smart Selectors
  • Handle XHR and dynamic content
  • Request/Response stubbing and mocking

Getting Started

Easy Installation

Taiko works on Windows, MacOS and Linux. You only need Node.js installed in your system to start writing Taiko scripts in JavaScript. After you’ve installed Node.js open a terminal application (or powershell in the case of Windows) and install Taiko using npm with the command

$ npm install -g taiko

This installs Taiko and the latest version of Chromium browser. We are all set to do some testing!

Interactive Recorder

Taiko comes with a Recorder that’s a REPL for writing test scripts. You can use Taiko’s JavaScript API to control the browser from the REPL. To launch the REPL type taiko in your favorite terminal application

$ taiko
Version: 0.8.0 (Chromium:76.0.3803.0)
Type .api for help and .exit to quit
>

This launches the Taiko prompt. You can now use Taiko’s API as commands in this prompt. For example, launch a Chromium browser instance using

> openBrowser()

You can now automate this Chromium browser instance with commands, for example, make the browser search google for something.

> goto("google.com/?hl=en")
> write("taiko test automation")
> click("Google Search")

These commands make the browser go to google’s home page, type the text "taiko test automation" and click on the "Google Search" button. You can see the browser performing these actions as you type and press enter for each command.

Taiko’s REPL keeps a history of all successful commands. Once you finish a flow of execution, you can generate a test script using the special command .code

> .code
const { openBrowser, goto, write, click, closeBrowser } = require('taiko');

(async () => {
    try {
        await openBrowser();
        await goto("google.com");
        await write("taiko test automation");
        await click("Google Search");
    } catch (error) {
            console.error(error);
    } finally {
            closeBrowser();
    }
})();

Taiko generates readable and maintainable JavaScript code. Copy and modify this code or save it directly to a file using

> .code googlesearch.js

You can choose to continue automating or finish the recording using

> .exit

To run a Taiko script pass the file as an argument to taiko

$ taiko googlesearch.js
✔ Browser opened
✔ Navigated to url "http://google.com"
✔ Wrote taiko test automation into the focused element.
✔ Clicked element containing text "Google Search"
✔ Browser closed

By default Taiko runs the script in headless mode, that means it does not launch a browser window. This makes it easy to run Taiko in containers (ex. Docker). To view the browser when the script executes use

$ taiko googlesearch.js --observe

Taiko’s REPL also documents all the API’s. To view all available API’s use the special command .api

$ taiko
Version: 0.8.0 (Chromium:76.0.3803.0)
Type .api for help and .exit to quit
> .api
Browser actions
    openBrowser, closeBrowser, client, switchTo, setViewPort, openTab, closeTab
...

To see more details of an API along with examples use

>.api openBrowser

Launches a browser with a tab. The browser will be closed when the parent node.js process is closed.

Example:
    openBrowser()
    openBrowser({ headless: false })
    openBrowser({args:['--window-size=1440,900']})

Smart Selectors

Taiko’s API treats the browser as a black box. With Taiko we can write scripts by looking at a web page and without inspecting it’s source code For example on google.com the command

> click("Google Search")

clicks on any element with the text Google Search (a button on the page at https://google.com). Taiko’s API mimics user interactions with the browser. For example if you want to write into an element that’s currently in focus use

> write("something")

Or if you want to write into a specific text field

> write("something", into(textBox({placeholder: "Username"})))

With Taiko’s API we can avoid using ids/css/xpath selectors to create reliable tests that don’t break with changes in the web page’s structure.

You can also use Taiko’s proximity selectors to visually locate elements. For example

> click(checkBox(near("Username")))

Will click the checkbox that is nearest to any element with the text Username.

Taiko’s also supports XPath and CSS selectors

> click($("#button_id")) // Using CSS selectors
> click($("//input[name=`button_name`]")) // Xpath selectors

Handle XHR and dynamic content

Taiko’s API listens to actions that trigger XHR request or fetch dynamic content and automatically waits for them to complete before moving on to the next action. Taiko implicitly waits for elements to load on the page before performing executing the command. Scripts written in Taiko are free of explicit local or global waits and the flakiness.

Request/Response stubbing and mocking

Setting up test infrastructure and test data is hard. Taiko makes this easy with the intercept API. For example, block requests on a page (like Google Analytics or any other resource)

> intercept("https://www.google-analytics.com/analytics.js");

Or redirect an XHR request on the page to a test instance

> intercept("https://fetchdata.com", "http://fetchtestdata.com")

Or stub an XHR request to return custom data

> intercept("https://fetchdata.com", {"test": data})

Or even modify data sent by XHR requests

> intercept("https://fetchdata.com", (request) => {request.continue({"custom": "data"})})

This simplifies our test setups as we don’t have to set up mock servers, or replace url’s in tests to point to test instances.

Integrating with Gauge

We recommend using Taiko with Gauge. Gauge is a framework for writing readable and reusable acceptance tests. With features like markdown specifications, data driven execution, parallel execution and reporting Gauge makes test maintenance easy. Gauge is easy to install and well integrated with Taiko. With Gauge and Taiko we can write reliable acceptance tests.

Install Gauge using npm and initialize an initialize and sample Taiko project using

$ npm install @getgauge/cli
$ gauge init js

Learn more about Gauge!

Experimental TypeScript Support

When using Gauge together with Taiko with gauge-ts using

$ npm install @getgauge/cli
$ gauge init ts

You can optionally configure your project to use our experimental type definitions. Edit your tsconfig.json and add the following lines:

{
    "compilerOptions": {
        // gauge-ts default configuration here
        // add experimental taiko TypeScript Type Definition folder to the project
        "typeRoots": ["node_modules/@types", "node_modules/taiko/types"],
        // use taiko types in the project
        "types": ["node", "taiko"]
    }
}

Documentation

Inspired by

Talk to us

Copyright

Copyright 2019 ThoughtWorks, Inc

You can’t perform that action at this time.