>>

OpenRunner

Using our OpenRunner tool, testers and frontend developers are able to carry out benchmark and automated functional tests more efficiently on frontend-heavy web applications. The open source tool acts as a browser extension, with which end users can be simulated through the browser. This means that OpenRunner is able to record functional changes with great accuracy and provide an exact picture of the response and processing times.

Why measure speed in the browser?

Performance test tools often only measure the end-to-end request response times between server and client. However, that does not include the browser processing. This used to suffice, because a web page was placed fully ready on a server so that it could subsequently be delivered to a web browser. But these days the logic is on the side of the client and far more calculations are expected from the browser. The speed of the site in the browser therefore greatly influences the experience of the end user as well.

OpenRunner addresses the browser in a way that connects up better with the latest techniques and standards, and at the same time represents an enormous improvement in respect of functional test tools such as Selenium. Moreover, it is possible to realise certain manipulations in the tested website, allowing the functional testing to work better and more reliably.

Testing functionality and performance quickly

By using OpenRunner a page can be loaded a hundred times in a row in order to measure the response time, including the processing and page assembly in the browser. This makes it possible, in the case of multiple changes to the website, quickly to see changes in the performance, even when rendering in the browser is heavier. In addition, by using ‘OpenRunner scripts’, the functionality of pages can be checked very quickly.

OpenRunner therefore makes the testing of frontend environments even more efficient.

Continuous Development en Continuous Integration

OpenRunner connects up with Agile and Continuous Development (CD) and Continuous Integration (CI). Therefore the tool can also be integrated simply in a CI/CD build street or environment.