In a previous post, we showed how we could track the duration of our existing automated functional tests, allowing us to detect any anomalies between different builds. However, to ensure that the system behaves normally under load, we need to generate simulated traffic and measure performance related metrics. One of the solutions that are growing in popularity is Gatling.
In this post we will explain how to modify our existing WebdriverIO tests to start asserting them against some performance checks. We will use the Timings library and view the performance measurements in Kibana.
Performance is a non-functional aspect which testers rarely have time to cover. In this post, I will introduce you to the Timings library which allows you to collect performance data from your browser as well as viewing it on a dashboard. This layer of performance checks can be added to your existing tests with minimal effort.
In this tutorial, I will introduce you to an amazing performance tool I have come across: sitespeed.io. The official website describes the tool as “the complete toolbox to test the web performance of your website.” Sitespeed.io gathers some popular performance tools in one place to get a clear picture of the state of your site in a matter of seconds!
In our previous post, we took a look at the current testing trends and tools, which help us identify the favorite packages and frameworks in our industry. In this post, we’ll try to predict the future based on the latest Google Trends, various articles, and webinars on the Internet.