Author: Davor Banović

How do you know if you have a critical bug?

In the old days we could qualify bugs in different scales – severity, impact, visibility, class and priority. This practice seems to be abandoned in favor of easier project management so there is frequently only one field. However, making only one field available for depicting bug importance hasn’t helped much in qualifying bugs critical or making decision on how soon is the fix needed.

Powershell tips for bash users, part 2, Day to day scripting

One of the best things in shells is that you can do some repetitive tasks quickly,…

PowerShell tips for bash users, part 1

Some software testers often write shell scripts to make life a bit easier. But real power…

5 reasons why exploratory testing may be better for your software project

There are lot of disputes about scripted vs. exploratory testing. Here is a modest attempt to…

Is Quality Assurance agile?

Users does not need to know the fancy name, but are mostly doing heuristics analysis when are introduced to new features. They are deciding is the software with new feature remaining consistent with its history, comparative products, intended use and so on.

Software testing adds a value to software

Every now and then in my daily work I recall wrong definitions of software testing and…

Software test help customers tell their story

Lately, in software development lifecycle, vastly formalized requirement documents are being replaced by more agile, so…

Got a project for us?
Let's talk.