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.
There is a concerning thought in development teams that testers solely own quality. Developers from time to time, tend to trust their faith blindly on their coding skills as well as the skills of testers by skipping their quick checks. It is a fact that testers are continuously trained and focused on preserving the quality of a product, however, remember that the output is the result of full team collaboration.
In the last couple of years, we have seen a boom of Node.js browser automation libraries using the Webdriver protocol. WebdriverIO is one of those libraries which has seen its popularity growing progressively due to some excellent features. Why don’t you give it a try?
Within the Agile world of Software Development, the tester has a ticking bomb in his hand. Quality needs to be maintained within a short timeframe. The Test Pyramid might provide guidance in making the most out of your test automation efforts.