Category: User Acceptance Tests

We often hear the phrase “prevention is better than cure”. It’s gotten a bit old over time, but that doesn’t make it any less true.

This phrase sums up the zest of the article you’re going to read now. Before you roll out any product, you always test it. You basically just make sure that everything you designed is there and it works exactly like you designed it.

Not long ago we published the post “Bug tracking explained in funny GIFs“. We had a lot of fun writing it and got a lot of positive reactions. Therefore, we decided to write another post about a topic that is equally relevant to us: User Acceptance Testing.

Many of our customers use Usersnap for User Acceptance Testing and we have written a few serious articles about this topic.

If you are new here: User Acceptance Testing is often the last step in software development. The idea is to test if a product works for the user. If you want to read more about how to get started with UAT we have some interesting articles for you. If are just here for the fun, read on! 🙂

When interacting with our customers and blog readers, we usually find that everyone has a different set of ideas on proper user testing workflows. Blame it on the inconsistencies when it comes to the terminology of User Testing, Usability Testing or User Acceptance Testing. The need for clarification on this topic is certainly huge.

In this blog post, I will try to bring some light into the fields of Usability Testing as well as User Acceptance Testing. I will also highlight the main differences of both areas. Check out what user testing is all about.

… or how to be the first one who gets going with agile testing.

When working on digital projects and products, you probably encounter the term ‘agile‘ a lot.

The word agile is widely used (and sometimes misused). It refers to the methodology of project management which strives to establish certain principles of collaboration, flexibility and transparency. It emphasizes the importance of feedback throughout the entire development workflow.

So when it comes to testing, web development teams go back to traditional approaches rather than following the agile path.

In this post, I’ll give you an overview on agile testing as well as some useful guides on how to get started with the idea of agile testing.
Continue Reading “Why no one talks about agile testing…” →

Smartphones seem to have taken over desktop computers in terms of usage. The number of smartphone users has increased tremendously in the last few years and by 2016, there will be more than 2 billion smartphone users. In addition, half of the internet’s usage comes from mobile devices.

This development affects also web design for some years. InVision recently stated in one of their blog posts:

“Responsive Design is no longer a luxury, but a necessity.”

Especially when it comes to testing, mobile website testing still is in its child’s shoes and developers face a hard time getting the best result out of their work.

In this blog post we are going to show how to set up the perfect mobile feedback & website testing workflow and how to easily conduct browser tests for mobile.

Making web applications is fun. Well, it should be fun, but it’s often not. It’s not, because there’s so many browsers, operating systems, and devices to cater to. And who has the resources to cater to every device configuration and operating system setup which the average user is likely to have? Can anyone truly cover them all?

Yet despite this challenge, it’s our responsibility to deliver the best possible experience; and to do that, we need to find a way to do reliable browser testing.

So in this post, I’m going to show you how to get started by providing you a step-by-step guide to cross-browser testing packed with tips, metrics and tools. When you’re finished, you’ll have all you need to start.