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.