In this post, we’ll dig a little deeper into TestCafe’s capabilities. To optimize the effort and reduce the execution time of our tests, we’ll run our tests in parallel in two different browsers!
A tool like Applitools used with BDD – really? If you do decide to go for the BDD approach, then you must be prepared for a change of mindset. Not only do you need to implement automated tests, but you also need to cater for the BDD syntax. This is the mindset I immediately had to adapt to when taking on such a task.
This blog post goes into detail of how I thought was best to integrate Applitools to our BDD Framework.
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.
TestCafe is a good alternative to Selenium-based tools. Since it injects itself into the website as JS scripts, it’s more stable and faster. This allows TestCafe to run on any browser, including mobile devices and Cloud Services as well. In our post, we’ll implement our first TestCafe test and run it on SauceLabs.
Security, a buzzword for some companies and a priority for others. We hear of so many security breaches, but we…
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.