menu

taiko

A node.js library to automate chrome/chromium browser

Channels
# All channels
view-forward
# General
view-forward
# Meta
view-forward
# News
view-forward
Team

Taiko's design principles

November 15, 2019 at 5:02pm

Taiko's design principles

November 15, 2019 at 5:02pm (Edited 9 months ago)
  • Web technologies for testing web applications. Taiko will only be available in JavaScript
  • Flat API's wherever possible. A single function call for e.g. click instead of fluent api's or objects or complicated page object models.
  • API's for the user, not the programmer. The api's and it's parameters must allow testing the browser as a black box without having to know the internal structure of the applications
  • Build for stability. Always look for ways to make api's and tests stable.
  • Have a plug-in architecture for features that need not be part of the core but is compliments Taiko usage
  • Optimise for performance
  • Work well with other frameworks. For examples runners, assertion frameworks. For this reason Taiko will not have it's own runner or assertion frameworks.
  • Work well on IDE's. For e.g. auto completion, viewing the api source code and documentation.
No messages yet