This is the second part of our Timings post. In this part 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 is much faster and more stable. 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 the amazing cloud provider SauceLabs.
Security, a buzzword for some companies and a priority for others. Sometimes knowing the basics can take you such a long way, that's why OWASP developed the Juice shop - an insecure application which lists vulnerabilities in a scoreboard, to solve as ‘puzzles’. The more weaknesses you find on the website, the more points you get.
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. Most of the time such issues will not be found straight away and may take quite some time for someone to fix. 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 analyze and deflake your flaky tests and make your Jenkins builds greener. We will go through both plugins in detail, helping you choose which is best suited for your CI pipeline.
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. 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.
Welcome to TestAutonation
TestAutonation.com is a space where Software Testers, QA Engineers, Software Developers and anyone with interest in anything related to Software Testing create, share and discuss exclusive content for the Software Testing community.
Our primary aim for starting testautonation.com is to not only create a one of a kind knowledge sharing platform but also engage one another with past experiences and insights into latest technologies.
We will start by releasing a series of blog posts but would like to organise MeetUps, Podcasts, Courses/tutorials and conferences in the future. The difference from other "communities" is that with TestAutonation anyone can write a blog post, course/tutorial or give a speech under the TestAutonation name.
So stay tuned for any surprises we have planned for the Testing Nation.
TestAutonation needs your help!
Have a request for the Test Autonation to write about a particular topic? Or maybe you want to become a Test Autonation author?
Then contact us straight away, and help the Test Autonation grow!