We have already wrote previously about how you can automate your testing routines without using the graphical interface but by using Loadero API instead. In this blog post we will show how you can integrate performance and load tests into your CI/CD workflows with the help of Github Actions. Github Actions allow you to automate and execute your development workflows directly from your repository which makes the integration very simple.

It can be a real headache to test contact forms or other outgoing emails from your website or application locally. To permit mail, you ought to configure your nearby web server and waste plenty of time expecting the mail to reach for your inbox, if it does at all. Furthermore, if you test with your personal email account as the sender, you risk damaging your email address. So, what should you do? You can use tools like MailHog and others, which are great for sending transactional emails.

Recently, k6 started supporting k6 extensions to extend k6 capabilities for other cases required by the community. The community has already built plenty of extensions. k6 extensions are written in Go, and many of them are reusing existing Go libraries. This makes k6 to be a versatile tool to test different protocols and adapt to multiple cases. This post is the third part of my series of articles testing various systems using k6: Let's look in this post how we test the popular Kafka project.

Load testing isn’t an engineer’s favorite task. Every setup choice made during performance testing will yield varying results. The chosen load test protocol is the difference between an application that performs well under most circumstances and one that buckles at hidden stress points. Yet failing to run adequate tests isn’t an option when dealing with a complex API architecture. Needless to say, all your load testing options must be carefully evaluated.

Mobile app testing can be time-consuming, error-prone, and sometimes expensive if not done the right way. But mobile app testing is a critical part of the development process, so skipping it comes at a huge cost to end UX. To compete with the millions of mobile apps on the market, your set of best practices must ensure that the user experience is incredible for every consumer every time they use your app, starting from the first try. Not sure where to begin?

The process of web development has changed its meaning in the time span of twenty years ( 2000 to 2021). Earlier the process was simple and just three technologies could do all the job. The competitors were less and the businesses were slow in adapting to the web application phase. On the client side, browser choice was not a luxury. Mainstream desktops had internet explorer with Netscape as an option but it was slower in capturing a significant share.