As you’ve read in our last blogpost about the story of growing Usersnap, the current times are quite exciting for us. We’d like to take this opportunity of Thanksgiving and stop for a minute.
Usersnap is growing steadily and today it is my pleasure to welcome two new team members:
The Usersnap team was working hard on some neat features for our 3rd party integrations in the last weeks. Besides our new Bitbucket integration we’re excited to offer you a pre-selection possibility for your connected tool. Learn more how it works!
For the 10th anniversary of the Firefox browser, Mozilla announced a new browser version explicitly for developers. We at Usersnap took a closer look at the new browser version. Read what we think about the new Firefox browser and if it keeps up with the Google Chrome dev tools.
On November 4th our COO Josef Trauner gave a talk about “ The Bug Reporting Time Machine for AngularJS” at the AngularJS Meetup Vienna.
[3 min read]
The whole Usersnap team has been working hard the last two weeks to bring you an awesome new communication experience. The Usersnap comment tool allows you to highlight an area and pin-point issues faster than ever.
In modern society we’re always on the lookout for new ways to eliminate waste and improve productivity. In our personal lives, and especially in day-to-day business, productivity improvements are seen as the holy grail, to be strived for and achieved each and every day.
We’re regularly inundated with new tips, ideas, concepts, software and strategies. But which way do we turn? How do we sort the good from the bad? Today I’m going to show you a way that’s as simple as its name is short, one which will help you increase productivity with a minimum of effort — it’s called Kanban.
Just a few days ago Github announced their new update of Github Issues. You can see the updates with some screenshots from here. Also, please take a look at the new Deployment API if you haven’t already.
Move beyond the simple Issues
Starting at the same day something else were released, not by GitHub, but still connected to Issues. Let me show you, how you can use a chain of tools to make your GitHub Issues even more useful for your team.
Imagine you have a website, that is hosted on Github, like this one, which is the code-base for input.mozilla.com.
Let’s also imagine that you have a team or a community which is handling bug-requests. You have a designer and a programmer at least.
These days being a developer isn’t an easy task. Among all the tasks and challenges you already have to deal with, you need to deal with bugs. And here’s the rub, most of the time bugs, specifically client-side bugs, are submitted by end-users. We see 3 key problems with this:
1: Most Users Are Not Tech Savvy
It’s true and whilst we not say it to them directly, we know it. The user knows something’s wrong, because the website is not working for them, but they don’t know why, how to fix it or how to report it.
It all started again with a tweet:
Anybody know of any good primers on bug reporting for less technical users who occasionally become QA?
— Michael Bailey (@roguewhaler) June 25, 2014
We have a person that knows something about the Internet and what is a website and this person should follow a test plan or just to do random testing.