Delivering quality at speed has become part of the quality assurance lexicon over the past few years. However, as manual work remains “unskippable” in different steps of our test cycles, the goal of running more tests in a shorter time might seem to be out of reach. Today’s article will walk you through the latest features of Katalon Recorder 5.6 and explain how they help reduce manual efforts and shorten your next test cycles.
What I see too often though is folks running multiple UI tests in an attempt to validate specific output values or logic. A much easier way to accomplish this task is to run specific API tests on the business logic of the software. Why should we do this? It’s much faster and easier to write these tests. We can have our developers supporting this process and not just Selenium or automation experts. 'Work smarter, not harder' is a theory we should all be familiar with.
The first-ever release of Selenium WebDriver 1.0 in 2007 has indented a lasting footprint in web automated testing. And through the years, the contributions of the Selenium project (WebDriver, Grid, and IDE) have truly transformed the way that we do quality assurance. Fast forward to the ‘drop-in’ release of Selenium 4 and Selenium 4.1, this article narrows down the top 5 changes you need to know for WebDriver, IDE, and Grid.
In part one of our series “How to improve quality as a team,” we talked about the effectiveness of adding shoulder checks to the agile development workflow and how that helps improve the overall quality of the product. This article introduces you to another fantastic exercise, you might be familiar, with called the user story kick-off. This practice helps larger teams align on more complex features, and in turn increase quality output as a team.
This post does not look at a particular aspect of JMeter nor does it give a detailed overview of how to use a particular tool that will compliment your performance testing with JMeter. What it is about is the principles of push to production pipelines and performance testing and while I have stated that this post is not specifically about JMeter in my experience JMeter is one of the best performance testing tools for this type of pipeline integration.
In this post we are going to look at WebSockets, specifically how JMeter can be used to test them. Web Sockets are not supported natively by JMeter but there are a couple of Plugins that you can use that work very nicely. One of them is called JMeter WebSocket Sampler by Maciej Zaleski and information on the library can be found here. The second and the one we will use for our post is also called JMeter WebSocket Sampler and is by Peter Doornbosch, more information on this Plugin can be found here.
There are many samplers that JMeter provides but I am willing to bet that the HTTP Request samplers is the most frequently used and, in this Blog Post, we are going to look at how this works and how it can be configured.
Congratulations on getting to part 4 of the “A beginner’s guide to test automation with Javascript (Nighwatch.js)” blog series! This part will help you to improve your test script (and make it cooler). We’ll explain different style suggestions and the overall script structure that we follow in Loadero to bring your script to a new level.
In this guide, we'll look at adding performance testing to your development workflow with Buddy and k6. k6 is an open-source load testing tool for testing the performance of APIs, microservices, and websites. Developers can use k6 to test a system's performance under a particular load to catch performance regressions or errors.
Here at Sauce Labs, we love Selenium. It was created by our co-founder Jason Huggins, so it will always have a soft spot in our hearts. But the truth is, if we are being technical, Selenium is more of a robotic browser control mechanism than a true test automation framework. While Selenium can definitely be part of your test automation strategy, the use of it in itself would not qualify as a proper testing strategy.
Automation testing tools are applications designed to verify function and/or non-functional requirements via automated test scripts. With the Agile and DevOps manifesto as the standard of software testing, setting a clear-cut automation testing tools evaluation strategy is key. Ultimately, this strategy will need to answer the questions of: Plus, there isn’t really a one-size-fits-all automation tool. It really boils down to your team’s specific needs.
Below are some key insights on how LoadFocus may help you with achieving your goals.
Can you believe that the holiday season is almost upon us? High time for an update from your trusted load testing provider!
If you’re in a regulated industry, you or your team has likely had to use Failure Mode and Effects Analysis (FMEA) for compliance. But because of the way regulated industries have to balance between the world of very strict quality standards and also high-velocity Agile processes, traditional FMEA has to evolve in order to meet the challenges that are arising in this new reality.
Recently AWS made the new ARM processors for Lambda functions generally available. With that change Serverless functions now use Graviton2, said to offer better performance at lower cost. I built a sample API on AWS using API Gateway and Lambda, and I wrote two endpoints, one CPU-intensive (calculating Pi using Leibniz's formula), the other a typical data transfer endpoint (returning an arbitrary number of bytes). Two very different endpoints for my experiment.
The software industry is transforming rapidly due to new changes brought on by artificial intelligence (AI) and machine learning (ML). AI & ML have democratized many aspects of the software testing process helping businesses, small and large, save time and money. As AI bridges the technical gap required in many jobs, more people will be able to add tremendous value to development teams — without the need of a computer science degree.
As 2021 winds down, we wanted to share an overview of the new things the Zephyr team did this year to help you get to the next level of quality – and offer a sneak peek at things to come.
Hello Katalians! Let’s go straight to the point, our latest release of Katalon Studio (8.2.0) is here, and it is awesome. For this release, we focused on speed and performance, and we are happy to announce that Studio now consumes less resources and gives more horsepower to your software delivery pipeline.
George Ukkuru is a seasoned technocrat and AVP of quality engineering, DevOps, and SRE @Marlabs Inc. Over the course of two decades, he has helped Fortune 500 companies implement Agile testing practices. He has also authored a number of books on quality engineering and test automation. In this QnA, Ukkuru lays out the scope and depth of his experience without even trying.
The software Quality Assurance role (QA) has traditionally been seen as a person who finds bugs and tries to break things. While these tasks still remain a big part of the QA’s role, the industry has seen a shift towards a more holistic approach where the QA role advocates for the overall quality of delivery — both product and process. Incorporating the exercise of “shoulder checks” into the agile software development lifecycle increases quality output.
Testing is the backbone of the Agile software development methodology. The efficiency of the testing process directly impacts the quality of the deliverables and the goodwill of the organization. Buggy software can lead to poor user experience, delayed project timelines, diminished brand value, and revenue losses. A strong testing process consists of several well-planned activities with definite timelines and a set of clear expected outcomes.
Free open-source frameworks, libraries, and tools are the go-to solutions for automation testing. The main difference between these is knowing your preference between creating your building a brand new test automation framework using libraries, or working on a made-ready tool where testing is all you will have to care about. This article gives you a quick glance at the Top 10 Free and Open Source Testing Tools, Tools, Framework & Libraries.
As a small business or a startup, we often make decisions that can change the whole structure of our working processes. Honestly, this is not a bane that can bring the businesses down. Such businesses thrive on these decisions as they let them clearly decide what suits them best and why. What’s better than finding it on their own by trying a mix of things? As for this post, it is a bit different from startups and small businesses.
In my 18 years of working in quality engineering and the testing community, I’ve developed some best practices to help organizations create and manage their overall test strategies. This is the second in a 10-week series on what testers wish their CIOs and CTOs knew about testing. Each week, I’ll share my experience to help educate tech leaders on key priorities their testing teams need them to understand.
k6 Cloud, our managed testing solution, supports Prometheus to store and correlate performance testing metrics within your observability stack since a while now. Announced at Grafana ObservabilityCON, we launched Prometheus support to k6 Open Source - our free, open, and extensible load testing tool. k6 OSS supports sending k6 metrics to multiple outputs such as InfluxDB, New Relic, StatsD, and more.
Even when seamlessly combining manual and automated approaches, testing every functional combination within web or mobile applications is challenging. Unfortunately, this means critical issues inevitably go undetected and make their way into the hands of your customers. We strive for perfect code, perfect releases, and perfect apps, but alas, perfection is a myth. With that in mind, if you cannot catch every issue before a release, at least you can take the proper steps to limit them.
Product failures and defects can occur on many different shapes and levels, impacting any part of the user experience, functionality, and even safety. In the past, organizations were taking the approach of of Failure Mode and Effects Analysis (FMEA) for risk assessment. This allowed teams to identify and prevent failure before a product or update is released.
Artillery is an open-source command-line tool purpose-built for load testing and smoke testing web applications. It is written in JavaScript and it supports testing HTTP, Socket.io, and WebSockets APIs. This article will get you started with load testing your Node.js APIs using Artillery. You’ll be able to detect and fix critical performance issues before you deploy code to production.
Embracing DevOps is not easy. There are a lot of misconceptions about what DevOps is. DevOps is not a team, or a methodology, or a job role. DevOps is a culture founded on a set of work patterns and practices that have an impact on the whole value chain, from business to operations. DevOps helps you move from only having visibility about your own work, to having a birds-eye view and overall understanding of the whole value stream (from business to customer feedback).
Late October, the Catalyze Tech Coalition released the Action to Catalyze Tech (ACT) report, which outlined best practices, accountability measures, and systemic changes needed to support workplace diversity, equity, and inclusion in the tech industry.
We’re excited to launch xk6-browser at Grafana ObservabilityCON today, an extension to k6 adding support for browser automation via the Chrome Devtools Protocol (CDP). k6 was built because we weren’t satisfied with the developer experience offered by existing load testing solutions. We believe in shifting performance testing, and with it observability, to the left.
In a perfect world, our dev teams would write flawless code and never make a single mistake (though I suppose I might be out of a job then.) The truth of the matter is software never is perfect. Mistakes, like Thanos, are inevitable. Moreover, testers shouldn’t be attempting to make the software perfect, just mitigate risk by protecting revenue and the customer experience. When we consider the overall customer experience this becomes easier to understand.
We recently announced Ably's Control API, a REST API that enables you to manage Ably's configuration programmatically. You can now use the Control API to configure anything previously only configurable via the Ably dashboard. The Ably platform is designed around four pillars of dependability: Performance, Integrity, Reliability, and Availability.
Hello Katalians! We are back with a new release of Katalon TestOps. The November 2021 TestOps release focuses on enhancements to the report system, including test results and changelog reports and improvements around test run reports, to bring you better insights during the testing process.
Testlio’s vision is imagining software experiences that energize the world. It’s a big vision and a big reason why companies like Amazon, Microsoft, Netflix, SAP, and ViacomCBS work with Testlio. This vision signals a responsibility that goes beyond delivering best-in-class testing services, bringing together a global network of expert testers, and building a platform that enables a new way of testing.
Many businesses are burdened by an excessive amount of testing data. In that circumstance, it becomes impossible to distinguish between what is valuable, and what is noise. Therefore, having an effective reporting system in place in your company will ensure that all data is properly gathered and transformed into actionable insights. This article will walk you through the benefits of test reporting, and the top 7 test reporting tools that are currently available on the market.
In my 18 years of working in quality engineering and the testing community, I’ve developed some best practices to help organizations create and manage their overall test strategies. This is the first in a 10-week series on what testers wish their CIOs and CTOs knew about testing. Each week, I’ll share my experience to help educate tech leaders on key priorities their testing teams need them to understand. This week, we’ll talk about the user experience.
In a perfect world, systems or automated tests would never fail – everything in software test reports would, literally, “go green.” And to add to the stress, failures don’t just always go our ways to fail for the same reason. There’s something different every time: bugs in the AUT, errors in the test case itself, or problems within the structure to cause timeouts during execution.
October is over and it’s time to share the newest updates to Loadero that were made during the month. We’ve been working on adding a WebRTC metrics table for a long time, and are very happy to announce that it is available in the results reports. This update makes it very easy to find out about some of the possible issues in video calls. While this might be the most important of the news, we got more stuff to let you improve your tests. Here is what we added to Loadero in October.
