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.
Open-source projects are not always as perfect and bug-free as we may wish. Since such projects have a lot of contributions, it is only natural that mistakes happen from time to time causing bugs to appear. Most of the time such issues will not be found straight away and may take quite some time for someone to fix.After considering all scenarios, we came up with two options: downgrade the version to the point where the feature was working, or contribute a fix. Unfortunately, the latter is not a popular choice, as most people in the industry treat open-source software as an enterprise product, with expectations that someone will fix the problem soon. We decided to be brave, and choose to dedicate some time to contribute to a project which we loved.
In this post, we will introduce you to two powerful Jenkins plugins, which can help you to analyze and deflake your flaky tests and make your Jenkins builds greener.
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!
Say you are writing an HTTP client and you are provided with documentation detailing the endpoints supported by a REST API hosted somewhere. One way to test this client is to hit the server serving the API. For whatever reason, you might not want to do this. You might just want to test how your client’s HTTP requests look like. This post will guide you through doing just that with the help of echo.js.
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.
If you have ever built or worked on a testing framework, then you probably experienced “Flaky tests”. Flaky tests are inconsistent tests which provide different results (pass or fail) for different test runs. In this post, we introduce some hints, where the cause of the flakiness can hide and will show some tricks, how can you reduce the flakiness of your tests.
Want to take your mobile automation tests to the next level? In this tutorial, I explain how you can easily integrate the popular mobile testing framework Appium with webdriver.io. I also give a small hint which I found useful to keep my tests as organised as possible.
How many times do we find old builds which are constantly failing? What should be done to the job? Delete it? Fix it? What about preventing it – This blog post is a simple tutorial for integrating Jenkins and Jira, in order to trigger job failed notifications and keep your jenkins jobs as sunny as possible.
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?