Author: Thomas Peham

Why we have to talk about client-side JavaScript error logging!

Web browsers got some superpowers over the last few years. The increasing speed of the browser engines has pushed browsers from being simple website viewers to a level where they are platforms executing our beloved applications like Gmail and Facebook day in day out.

Of course, this opened up the door for developers to do incredible things. But just like with everything that’s new, chances are high that bugs and issues occur. A lot of times, client-side errors give developers a hard time in reproducing and finding the bugs.

In this blog post, I’m going to show you why client-side JavaScript error logging is easy to implement and that it is just a few clicks away 🙂
Continue Reading “Why we have to talk about client-side JavaScript error logging!” →

7 most important bug reporting skills every QA agent should have

A while ago, someone asked me: ”Thomas, what skills do I need to have when tracking bugs and joining a QA team?”

I was astonished by the question and more importantly, quite disappointed that I wasn’t able to come up with a great answer.

But it made me think. And it pushed me to do some research and to exchange ideas with other people in the bug-reporting world.

And today, I’m happy and ready to answer this question. Here are the most important bug reporting skills you need to have.
Continue Reading “7 most important bug reporting skills every QA agent should have” →

Why a bug report isn’t enough.

OK, I get it. You have an excellent team of developers, designers and project managers. You develop a great piece of software for a client. And you test it. Of course.

That is one awesome application. But then, when the application reaches the client’s end, bugs are popping out everywhere. Boom.

Despite all your best efforts, bug reports are coming in. So what’s the issue here?

Continue Reading “Why a bug report isn’t enough.” →

What we learned from prototyping with Facebook Origami

We at Usersnap are always looking for new ways and workflows in order to be more productive.

This week our UI / UX designer Benedikt worked on some new design drafts. Instead of using a traditional approach of prototyping we ended up using Facebook Origami.

In this post we are going to share some key takeaways and lessons learned for getting started with Facebook Origami. Check out our Facebook Origami review.

Continue Reading “What we learned from prototyping with Facebook Origami” →

Should you outsource website testing?

OK, I get it. Everyone wants to get high quality at no cost. Right?

It is particularly in software that we see a clear trend towards outsourcing. This is nothing new.

Because of the increasing average salaries of developers and the difficulty in finding qualified engineers, many companies are welcoming the idea of outsourcing.

When it comes to testing, outsourcing might also look like an easy win. Promised high quality at no (internal) costs. Awesome.

But before you consider outsourcing for your company, I recommend that you ask yourself the following questions.
Continue Reading “Should you outsource website testing?” →

Deconstructing User Testing

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.
Continue Reading “Deconstructing User Testing” →

Hands-on experience with Hugo as a static site generator

Many years ago, we launched bugtrackers.io as a small side project. Since then, the site has grown from a three-pager to a website with dozens of interviews.

The increasing number of pages & therefore line of code made us look for ways to improve our internal workflow.

We also ended up using GoHugo as our main website framework for bugtrackers.io. In this post I’m going to share some of our first experiences with GoHugo as well as our path to ending up where we are right now.
Continue Reading “Hands-on experience with Hugo as a static site generator” →

Why no one talks about agile testing…

… 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…” →

A beginner’s guide to Pivotal Tracker: How to boost your Pivotal Tracker projects!

When working in agile development teams or web agencies, you are probably always on the look-out for new and better productivity tools. Pivotal Tracker might be one of these tools which can help you become a better and faster team.

In this post, you’ll find everything you need to know when getting started with Pivotal Tracker. You will also find some useful tips & tricks on how to get more out of your Pivotal Tracker projects.
Continue Reading “A beginner’s guide to Pivotal Tracker: How to boost your Pivotal Tracker projects!” →

Fundamentals on setting up your bug reporting workflow

With all these emerging new devices – from mobile devices, to wearables, to VR, to smart devices – having a proper bug reporting workflow in place becomes quite a challenge.

Building web applications in particular might seem quite painful due to the different screen sizes of the used devices. It can even be worse than testing native apps for the Android ecosystem.

In this post, I’d like to show you different ways of setting up your bug reporting workflow. Including manual, automated and crowd-sourced workflows.

Continue Reading “Fundamentals on setting up your bug reporting workflow” →