This year’s TYPO3 conference was held in Amsterdam and Usersnap participated for the first time. After two exciting days of talks and great sessions, I’d like to give everyone a peek into the TYPO3 universe.
This is not a review of any particular talk or session but more of a personal glimpse into the world of TYPO3.
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.
A while ago – in April 2015 – 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.
… 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.
Two weeks ago, we announced a huge product update at Usersnap. Besides having the all new dashboard, we’ve also reimagined our Chrome extension.
We’ve rebuilt the Chrome extension from the ground.
Here’s how to be more productive while collecting website feedback & reporting bugs with our new Chrome extension and why you should definitely check it out.
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.
The last months were spent by the Usersnap team on building an all new Usersnap Dashboard with so-called Personal Lists which are announced today.
We’re super proud what the whole team achieved and like to show you some insights on building it.
The new Personal Lists will not only help you to be faster in your daily work with Usersnap. It’s the most personal Usersnap product update, ever.
With personal lists, bulk actions, an optimized search and many more improvements, we re-build the dashboard, making it easier for you to get more out of it.
Check out how to activate the new Usersnap dashboard and how to create personal lists.
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.
This article is brought to you by Usersnap, a bug tracker and feedback tool that helps you to communicate visually. Get a 15-day free trial here.
When you’re starting out, going to university or starting to work in your first full-time job, you feel like you can handle anything. You want to be a good developer, so you want to go full stack.
What’s that exactly? Well, bring together all the books relevant to information technology and bundle them together. That tower of information is what you’d call a full stack 😉
So, once you realize that, ambitious as you are, you know deep down that it’s probably a pipe dream. Or is it?