Today, there are 1.88 billion websites on the internet and the number is rapidly increasing. There are 3.8 billion people in the world that own smartphones today – which amounts to 48.16% of the world population. The internet traffic from mobile (as compared to that from desktops) has also been increasing, and now stands at 56%. The point I am trying to make is that if you have a website – it can be accessed from a web browser or a mobile browser.

Today, according to w3c, the most frequently used browsers are Chrome, Edge, Firefox, Safari & Opera. It is always advisable to run cross-browser test cases at least on these. However, the process of analyzing and selecting the thousands of device, OS, and browser combinations requires time, expertise, and effort too. Additionally, deciding which cross-browser test cases are ideal for automation requires proper analysis and expertise. Let us explore a few of such cases in this article.

Let’s start this post with a situation. An organization working in the logistic business has started to gather positive reviews and millions of users are now opting for their services through their mobile app. In other words, the organization is scaling very fast. Even though they were managing quite well with manual testers and in-house test automation setup, they know this arrangement cannot work for long. They are smart people.

Companies looking for digital transformation need to set up their teams for success. Modern development teams can release faster using an innovative suite of testing solutions. The integration with Xray and Functionize fits seamlessly into agile Jira workflows and incorporates AI/ML to speed up testing. The Xray-Functionize integration provides you with easy creation of automated tests, more visibility into testing results, and the capacity to increase team collaboration.

The experience your customers get once they enter your website can be a game changer for your online business in terms of sales, revenue, customers interaction and overall experience. Once you release new features for your website or blog, or once you add new plugins or widgets, add new styles, animations or functionality, all these can affect the Performance, SEO or Accessibility of your website.

Payments testing mimics each step of the payment process to verify that connections, transactions, and paths for communications are working. The best payments testing strategies include a thorough range of tests, from functional to performance to location. Need a place to start? Follow this checklist when developing a payment gateway testing strategy. A good strategy should detail exactly what information is needed, common flags for problems, and the markers of a successful payment gateway.

Without payments gateway testing, you risk cart abandonment, over or under-payments, penalties, and increased customer support costs. These risks occur when web or mobile app payment transactions run into issues. To avoid these issues, online retailers should create test cases, conduct periodic checks, and update their processes to ensure the system’s integrity. From functional testing to usability testing, there are many ways to test payment processing.

Cross-browser testing is performed to be sure that your product is working as expected on the various device, platform, and browser (and their versions) combinations that your customers might be using. With a plethora of devices and their versions in the market, it is integral to perform stringent cross-browser testing to attain a good market capture. Is it easy? No! Is it necessary? Absolutely yes! However, the pain and efforts associated can be reduced, if the cross-browser testing is cloud-based.

The whole point of cross-browser testing is to deliver consistent user experiences across various browsers. When we build websites or web apps, some of their features aren’t compatible with some browsers; with cross-browser testing, we can ensure uniform experiences. While performing cross-browser testing, we generally check for the following: When we perform cross-browser compatibility testing, it’s easy to discover such bugs and fix them before our product goes into production.

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?

In early 2016, Signagelive—a digital signage company—had an informal approach to QA. When developers had time, they performed a few manual tests ahead of each software release and hoped for the best. This allowed the company to focus on growth and building new features, but the company reached a point where the number of bugs clients found was unacceptable.

The goal of this getting started guide is to help teams get Jenkins continuous integration (CI) servers configured, and discover how to make a newly deployed CI infrastructure fully operational. Jenkins is a leading open source CI server. It is flexible, providing hundreds of plugins to support building, testing, and deployment, and is capable of automating any project. Jenkins CI infrastructure can be deployed to on-prem, in the cloud using configuration management tools, and third-party vendor.

The summer break is over, we start to creep towards autumn, and we at k6 haven't been resting on our laurels. What happened since the k6 v0.33.0 release? So glad you asked! The below. And then some!

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.

Only people who are living under the rock aren’t using mobile phones for their daily activities. Well, this means we all rely on our phones for things such as booking tickets, consuming multimedia content, or even ordering groceries and medicine. On average, most of us read, interact, engage and learn from the widely available resources like websites, mobile apps, etc.

According to Gartner, in the second quarter of 2021, mobile phone sales reached 328.8 million units with an increase of 10.8% year-on-year growth. It is remarkable and quite expected too! This outlines the need for using cloud-based automation platforms for mobile testing. Because when we are dealing with huge numbers and a global audience, it is the best bet.

After the closure of the influential Epic v. Apple trial, a California judge has ordered Apple to immediately remove its anti-steering rules, which barred app developers from offering payment methods outside of Apple’s in-app purchasing system.

The three key positions in a software development team are developer, tester, and operations. Required tasks among these positions are continuously changing and evolving and are continuously changed and reinvented. To speed up the development process, development and operations were integrated, which is now referred to as DevOps. Unfortunately, a critical layer between Dev and Ops was overlooked: the fixed cycle of testing.

Picking the right performance testing tool can be a challenge. What should you look for and what is important? Performance testing is a phrase many developers have come across at some point, but what is it exactly? In simple terms, performance testing is a software testing practice used to determine stability, responsiveness, scalability, and most important, speed of the application under a given workload.

You can find a collection of k6 scripts and build specification for CodeBuild in this tutorial here.

Don’t worry. DevTestOps isn’t another new term to create turbulence in our IT and DevOps world. Similar to other topologies like DevSecOps, which emphasizes more on the “Sec,” or security matters, DevTestOps stresses the aspect of continuous testing and CI/CD in DevOps. At the same time, to uphold the culture of saying “no” to working in silos, the DevTest approach specifically aims to end the lasting bad blood between the development and testing teams.

Cloud testing, in simple terms, means testing software applications using the resources provided by the cloud. Resources can be any element i.e., hardware, software, or infrastructure which are necessary to carry out tests. Cloud testing helps an organization gain competitiveness by reducing the cost of testing. By using cloud computing services for testing, organizations or businesses can shorten the provisioning time.

So, you’re interested in reaping the rewards of API and automation, but you don’t know where to start? Have you heard people using the term “API” and wondered what it is? Maybe you have a vague idea, but you still have no clue what to do with one? You’ve come to the right place! We pulled together this terminology to help you gain a basic understanding of web services and web API, which will also help you grasp the major concepts of API Testing.

Cloud-based technologies are on a rise today. Even if I deviate a bit from core IT fundamentals, the pandemic of 2021 made cloud tech a hero. It taught us how just an easy monthly subscription can give us access to thousands of movies, games, and live events such as the Tokyo Olympics via streaming. This is just a small example that we all can relate to and understand the cloud. In IT, however, the cloud means a lot more than just streaming media on the system.

You have likely identified a need to scale or improve your current software testing approach. But questions remain. Do you hire in-house testers? Do your engineers need to shift left and take ownership of code issues? Or, do you augment testing with crowdsourced QA or another type of app testing service? For many, the most efficient approach to scaling your testing is through a partnership.

Cloud-based technologies are increasing day by day. I remember what cloud meant to the people 10 years back and what it means now. It has grown more than just being “saving your files” to “developing on the cloud”. Cloud technology is almost everywhere today. From game development to machine learning projects to neural networks to automation testing- everything is on the cloud. And honestly, why shouldn’t it be?

This article is a step-by-step guide on how to run your end-to-end testing for React Native apps with Detox and Bitrise.

DevOps is all about collaboration and efficiency. The intent is to speed up the software development process to bring the products or services faster to the market. DevOps methodology focuses on standardising the development environment to deliver updates, upgrades, and security features to the end-user more quickly, improving customer privacy and security. So, what DevOps tools should you master?

August 7, I joined the Office Hours our Developer Relations team runs on a weekly basis, to talk about how we work at k6. We are growing rapidly, and are a little unconventional in how we organize ourselves, so I thought it would be a good idea to share in more detail how we build and ship software, being a remote-only company.

Automated web testing is not a new concept today. With advancements in web development technologies and how complex web codes are written today, web testing was bound to walk this way sooner or later. The problem with adopting automation is that it is not like a Netflix subscription that we can pay and enjoy cloud services. Climbing the automated web testing ladder requires planning, careful execution, and a workforce that is familiar with all the intricacies.

Web accessibility testing, also known as digital accessibility testing, is a subset of usability testing that ensures anyone can access and use your digital content (website, apps, etc.) at any time. This includes people with disabilities such as vision, hearing, literacy, physical, and cognitive disabilities. With around (or over 1 billion people) living with a disability, the calls for inclusion are growing louder by the day.

September 1, 2021 — Testlio, the originator of networked testing, today announced version 3.3 of its Platform. Testlio 3.3 introduces multiple new features and capabilities. While the new version provides many client benefits, several important features support freelance testers, the driving force behind Testlio’s business.

When implemented right, shift left testing can really help organizations achieve their quality goals faster and better. And to help that along, a valuable tool is needed too. All test automation tools are not made to shift your testing left so this is a crucial decision. In this blog, we will discuss how Testsigma supports shift-left testing. Let’s start by clarifying what is shift-left first.