As you’re probably aware, C# is a modern, garbage collected language, which means you don’t have to take care of object disposal as you would in languages like C++. However, that doesn’t mean.NET engineers don’t face memory problems, such as memory leaks. In this post, we’ll walk you through the basics of memory leaks in.NET: what they are, how they occur, and why they matter.

You have just clicked the button to run your test, but how soon will the first participant start the test? And when will you be able to explore the results reports? Each test run goes through multiple stages before a results report is generated. In this blog post we are going to explain everything you need to know about test run statuses you can see in Loadero!

Rahul Parwal is a software engineer, speaker, mentor, and writer out of Jaipur, Rajasthan. He has dabbled in software development, testing, and automation, and often shares his learnings in his blog. In this QnA, Rahul makes the point that a randomly failing test is always worth investigating and that assumptions are dangerous in testing.

Historically, software development and quality assurance were one and the same. If you built it, you also tested it. But then software grew up, and as it got more and more complex, dev and QA needed to split up in order to do their job right. But instead of these two teams remaining close friends, they grew far apart. Each in their own world, operating in different environments, using their own workflows, speaking different languages.

Not all apps are made the same. Native mobile apps, web mobile apps, hybrid mobile apps and progressive web apps (PWAs) are different in many ways. When choosing the right type of app for your business, you’ll want to carefully consider the advantages and disadvantages of each, then make sure you use the right testing approach. Below, we explain how these four types of apps vary, how to choose the right app type for your business, and what that means for your testing strategy.

Every new software, method, or tool comes with certain growing pains and takes some time to get used to, although it’s almost always worth the adoption effort, a major part of which is testing. Test automation dramatically improves your processes, saves you time and resources, and ultimately leads to higher-quality software. But you can’t just jump into it and expect the automation to produce the results you want.

To achieve success in product development, your teams must be aligned on clearly defined business criteria. If your teams are not marching to the same drumbeat, you significantly increase your risk exposure around quality issues and threaten your ability to hit deadlines. So how can companies ensure alignment? One popular option is incorporating business acceptance testing into existing workflows.

A test plan outlines the objectives, methods, organization, and success criteria for testing a specific feature of a web application or other software project. A good test plan contains all the information you need to write automated tests and will help direct your efforts so you don’t waste time creating unnecessary tests. Here is the test plan template we use with our clients.

Mobile testing is the process of testing mobile applications for functionality, usability or performance through the use of tools or open-source frameworks. Smartphones, tablet PCs, or every new release of the iPhone with the smallest changes, makes mobile testing, and automated testing, imperative to detect regression bugs and enables teams to ship quality applications.

Software testing was initially a manual activity, however, due to the importance of speedy delivery, the transition to automation testing is predictable. Unfortunately, this shift can become an overwhelming voyage, especially for startups without a dedicated QA team. Suppose you are a manual tester (or developer) seeking an automation solution to speed up your project.

At Speedscale, we are on the cutting edge of defining autonomous testing for the cloud era. However, we aren’t the only company trying to solve this problem and we enjoy learning from every perspective. That’s why Facebook’s recent blog article about autonomous testing caught my eye. They’ve built a sophisticated autonomous test system that introduces many of the same techniques we utilize.

Although terms like “quality testing” may seem modern, software testing has been around since the advent of computing roughly 70 years ago. Harvard University scientist Grace Murray coined the terms “bugging” and “debugging” in 1947 when a literal “bug” — in this case, a moth — got stuck in the computer circuitry and interrupted a connection.

Testlio is a globally distributed company with over 150 TestLions working from more than 20 countries around the world 🌍. While many companies had to quickly transition to a remote model in 2020, at Testlio it has always worked this way — we’ve been distributed by design ever since we started back in 2013. So, what is it like working in a distributed-by-design culture?

In this series, real (and really good) QA practitioners use their experience to support—or debunk what you might know about software quality. James Espie is a test specialist, a quality engineering proponent, and a continuous learner from Auckland, New Zealand. He shares his insights and sporadic bursts of inspiration in a hilarious newsletter called Pie-mail. If you haven’t seen it, you should check it out.

We all want our websites to be responsive and useful. However, the biggest correlation between website performance and business results is seen by improving the performance and speed of your website. Users get bored if they have to wait for too long to load your website or application. Performance Testing and Load Testing your website and restful APIs will help you understand better how your website and web services behave when a lot of users access your website at the same time.

The Kingdom of Quality is in disarray. Everyone works in silos – developers, testers, and other stakeholders. Communication between teams has faltered, making project collaboration nigh impossible. It’s as if goblinkin are at the helm. The damage is inevitable. Buggy releases, missed deadlines, and – worst of all – disappointed customers. It’s time for a quest. It's time for Zephyr Quest.

When someone new joins the company, they're encouraged to do what is called a "Week of Testing" - taking k6 for a spin and presenting your findings to the rest of the team. This article will show you how you can make your test scripts more readable and maintainable. To do that, I'll test a demo application with a custom DSL. DSL is short for a Domain Specific Language, and in this case, it allowed me to write meaningful code specific to our business requirements.

Did you know that an average user takes only 0.05 seconds to form an opinion on a website? Yes, Sweor’s study on website statistics shows that users decide whether they want to use a website or not in a fraction of a second. We can also note that about 57% of the global population doesn’t recommend non-responsive websites in the same study. In general, most websites or web apps run into errors because of a solitary reason: solid cross-browser testing isn’t performed.

Whether you’re building web or mobile apps, quality assurance is a non-stop cycle of corrections, updates, and improvements. And, QA takes time. But with crowd testing, you can quickly identify software issues, fix them, and release them with confidence. Some call it crowdsourced or crowd testing. Testlio calls it networked testing. It’s an efficient way to utilize a crowd of testers to ensure complete coverage.

In the face of increased demand and competition, software development teams are expected to iterate faster each project sprint. Iterating faster creates a market advantage because it means you can adjust quickly to evolving market conditions, changing end-user sentiment, and an unforeseeable black swan (like a global pandemic). However, increased software delivery speed cannot come at the expense of a high-quality end-user experience.

Both manual and automated testing have their place in the software development lifecycle. Understanding the pros and cons of each testing method — and the tools available for each — will help you find the most effective balance for your team.

Selenium 4 uses the W3C WebDriver standard protocol for browser automation. As browser vendors will only support W3C WebDriver in the future, using Selenium 4 ensures the widest possible range of support across all browsers, making your automation scripts future proof.

Several new features and benefits for automated testing are included in the upcoming Selenium 4 release, such as: Selenium 4 has been designed to be a drop-in replacement, but there might be cases where tests or dependencies need to be adjusted. We recommend you to go through the following sections to understand better how this new version will benefit you and what potential changes might be needed to upgrade.

In today's competitive market, you can’t afford to risk poor product quality and software failures. Unfortunately, many companies still use outdated methods to manage their tests like Excel, Word, Google Sheets, or other spreadsheet tools. Without a proper test management app, your quality suffers and testing remains archaic and at the most basic level, tracking and logging tests.

With the rise of virtual production, creative pipelines are becoming increasingly complex, and dispersed. Team members around the globe need to collaborate remotely. This can create security vulnerabilities, which can range from misconfigured SSL settings to expiring certificates. To help studios protect what matters most, the Trusted Partner Network (TPN) created an evaluation process to standardize fundamental security protocols, across the industry.

An automated testing strategy answers the who, what, when, why, and how of software test automation. While automation can be used for many kinds of software testing, in this post, we’re going to focus on the steps you should take when developing a strategy for functional UI testing (also known as end-to-end testing). End-to-end testing simulates real user conditions to test the functionality of an application from the front-end user interface.

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

Over the past few months, I’ve been redesigning and writing StatusCake’s SSL monitoring feature from Node to Go. This blog post describes one of the more subtle challenges we came across to help you master it if you find yourself with it too! Writing a Go client that fetches an SSL certificate isn’t a new problem. A common approach is to use a http.Client. This limits you to just certificates served over HTTPS, when technically anything running TLS can have a certificate.

Last week, Perforce announced our 12th acquisition, the BlazeMeter Continuous Testing Platform – a great addition to our DevOps at Scale portfolio. I’d like to welcome the Blazemeter team to the Perforce family. Throughout our conversations leading up to the acquisition, it was clear that we were dealing with a world-class product, and a world-class team. We are excited to add both to Perforce and look forward to the things we will accomplish together.

The goal of automating UI testing is to speed up the software release process and help developers catch front-end bugs sooner and fix them faster.‍ The potential benefits of automated UI testing for web applications are huge: Most software companies do UI testing by asking developers or QA engineers to write test scripts to test the front-end of the application within a web browser. The most popular automation frameworks are Selenium and Cypress.

September was a busy month for our team. With some of the vacations still happening, we worked hard to make our tool even better for you and also created and ran tests for some of our customers. While work on some features is still in progress, in this blog post we share what was changed in Loadero in September.