Your clients look to you and your agency for functional, appealing websites. As the creative pro committed to customer satisfaction, you and your company must balance that goal while maintaining an efficient communication flow that allows you and your team to do your best work.Continue Reading “Save 35% Communication Time on Client Approval with Usersnap Board” →
I wish I can just send a video screen recording.
Please delete this sentence from your vocabulary. Because we’ve heard your wish loud and clear, and we’re excited to announce Usersnap is your wholesome user screen recording feedback tool.
You can now see the entire flow of your users’ issues and save time in clarifying the steps of troubleshooting. Plus, your customers also save time in explaining what their screenshot means. Win-win.Continue Reading “Must try: User screen recording eliminates customer feedback confusions” →
Let’s talk about Quality Assurance: I’m super happy to work with a company that puts a lot of energy into the quality assurance part of every single software development project.
Quality assurance is a discipline that’s overlooked and under-appreciated. We produce software, share it with the team, test it, collect feedback, ask beta testers and then do it over again. Share, test, collect, ask, repeat. Yup, that’s pretty much it.
Yet people treat quality assurance as something superficial – a few tests here, a few user feedback there, and with one big eye staring at the release button.
Continue Reading “In praise of QA: What is Quality Assurance?” →
The methodology of User Acceptance Testing (UAT) is pretty straight-forward. The implementation itself requires some in-depth knowledge on the available types of User Acceptance Testing, though.
User Acceptance Testing is the process of verifying that a created solution/software works for ‘the user’. This might sound easy enough but, in practice, it isn’t.
To make your journey into User Acceptance Testing a bit easier, we researched the 5 most common types of User Acceptance Testing you have to consider.
In the last couple of weeks, we’ve given you a deeper look into the world of User Acceptance Testing. And over this period of time, we have received questions on the workflows and processes behind UAT.
It’s quite a special topic for us too, since our bug tracking- & testing software is used by a variety of people and companies helping them in their User Acceptance Testing efforts.
In today’s blog post I’d like to show you what the actual workflow of UAT looks like. From planning to executing and to analyzing your UAT efforts.
More and more web applications are being developed these days. And with each line of code being written, the potential for bugs arises.
Generally speaking, the costs of fixing bugs increase exponentially the later you find them.
The Systems Sciences Institute at IBM found that “the cost to fix an error found after product release was 4 to 5 times more than one uncovered during design, and up to 100 times more than one identified in the maintenance phase”.
And a study by the University of Cambridge found that software bugs cause economic damage of $312 billion per year worldwide.
These numbers highlight the importance of finding bugs as early as possible and to thoroughly test an application before it is released.
That is where web application testing comes in. Web application testing usually consists of multiple steps that ensure that an application is fully functional and runs smoothly and securely. It is an essential part of web development and ensures that an app is running properly before its release.
We put together a 6-step guide, which should give you an overview of what kind of tests to run to test your app.
Let’s get started!
Most developers have no clue about how testing is actually done, and how valuable the understanding of software testing basics can be for developers who really want to excel in their careers.
I owe a large amount of the success I have had in my career as a software developer to my background in testing.
Because I learned it the hard way.
Beta testing and User acceptance testing (UAT) are two of the most common types of tests to validate your development before launching your SaaS product or website.
“Do I need to perform both? What’s the difference?” you may ask. In this article, you’ll read about the different use cases of the two and get guidance on setting up these testing processes and their environments.
Shall we?Continue Reading “Beta Testing vs. User Acceptance Testing: When to use which?” →
Sometimes I feel a bit overwhelmed by the sheer amount of content in the field of project management. Especially when looking at the tool-side of project management. I see new tools popping up every other day.
With Jira and Trello – we looked at two major project management tools, their benefits and drawbacks and most importantly their main differences. Since Atlassian, the vendor of Jira acquired Trello, both project management tools are coming from the same company. But they are still competing over the same target group.
So if you’re thinking about making the switch to Jira or Trello, this article is the right place for you.
Continue Reading “Jira vs Trello – an Overview on the Best Project Management Tool” →
Bold statement right? But of all forms of testing, user acceptance testing is often the most essential to get right. Why? Because when implemented correctly, it’s the most effective in reducing both time and cost, whilst increasing customer satisfaction.
Continue Reading “User Acceptance Testing – How To Do It Right!” →