Taiko - Simplify your browser automation
Introduction
Why Taiko?
Limitations
Taiko plugins
Workshop
Free and open source browser automation tool
Node library automate the chrome browser
Uses the Chrome DevTools API
Simplicity
No Jars. No servers.
Simple APIs
Smart, Reliable, Maintainable
Smart selectors (wyswyg)
Proximity selectors (toLeftOf, to RightOf)
No more inspection
No sleeps, no waits (implicit waits, XHR handling)
REPL - Generate code
Taiko
CRI
CDP
Taiko features can be extended via plugins which can allow users to take more advantage of CDP when core Taiko concentrating on functionalities around UI automation tests.
Taiko-paypal, taiko-diagnostics, taiko-screencast etc
They help simplify workflow so users can focus on writing the the main UI automation
What taiko plugins do for us
Examples of existing plugins
Conventions
Plugins should have the prefix taiko-
Plugins should not have taiko as their dependency
Should implement the init() method on load which passes the taiko and event handler instances
Taiko can communicate with plugins via events. Eg: sessionCreated, firstMeaningfulPaint
Steps
... And the preliminary setup is done!