End to End Monitoring and Testing

Behavior and performance validation of basically every application. Test like a real-world user.

The Pinnacle of Testing!

Getting started

Icon symbolizing a UI end-2-end test on web- and native applications

E2E Testing

UI testing for web, native and OS specific user interfaces. Test easily, cover everything!

Learn more
Illustration of a display showing monitoring graphs

End to End Monitoring

Ensure reliable processes and monitor your complex system architecture!

Learn more
Robotic Process Automation illustrated as gears

RPA

Process and workflow automation by closing gaps and controlling tools!

Learn more
A Venn diagram showing that the intersection of selenium and nut.js is Sakuli

DOM and Native Testing

Sakuli improves Seleniums technology for web automation (in real browsers) and extends it with the power of Nut.js to emulate any other possible user-interaction, like opening rich-clients, typing and moving the mouse.
Sakuli shown as an open End-2-End Testing Platform

End2End Testing and Monitoring

Sakuli is an open platform for a variety of e2e scenarios including UI-testing, monitoring, Robot-Process-Automation or any other kind of automation. Sakuli will enable you to simulate the interaction of a real user with your target systems - check the availablity of your Citrix applications from different sites, ensure your conversion-rate in your web-shop or simulate and automate whole business processes throughout your Web, Windows, Mac-OS and Linux landscape.

Future-proof Architecture

Sakuli was originally created as a proof of concept for UI testing in a monitoring context. From this successful start, Sakuli kept growing and eventually became an open source product. But as time passed, with new web-technologies emerging and browsers getting more restrictive, some of the fundamental technologies of Sakuli grew old. Especially the web evolved a lot faster than the open source version of Sakuli’s underlying web automation framework with its proxy mechanism and security policy issues. So we had to decide whether to try and build a workaround for every shortcoming of the architecture or to build something new and future-proof, including the best downwards compatibility we could achieve.

We decided that time had come for something new… Since the language for tests-cases had always been javascript (executed in the JVM-based Nashorn - which is going to be deprecated), Node.js was the technology to go forward with. Sakuli 2 now focuses on an open platform-like architecture to provide a future-proof infrastructure able to grow with future web standard developments.

Sakuli 2 has been rewritten from scratch to be:

  • sustainable and future-proof
  • open and extensible
  • easy to use
  • compatible with Sakuli V1.x