I’m sure you are familiar with the term Technical debt. We’re all familiar with the ever going debates when designing and programming software – should we do it the ‘right (and long, expensive) way’ or maybe we should take the easier, faster road, which will get us quickly to a working new feature/product but also […]
Some Thoughts about The DevOps Era
Developing and releasing software is a complicated process. Applications now-days are more complex, and deployment infrastructure complexity grows, so are teams working on software projects.
Developing, testing, and releasing software quickly and in a consistent way, is therefore more challenging than ever. One way organizations face this challenge is to […]
In theory, we’re all supposed to be on the same page. In the quest to deliver stable builds that excite end-users:
Software testers are in charge of finding and reporting bugs.
Software developers are responsible for fixing those bugs.
It all sounds pretty straightforward.
But the reality is often very different.
There are times when developers don’t devote as […]
At Testuff, we talk a lot about finding defects. But what about fixing those bugs after you’ve found them?
If you regularly follow this blog, you already know how we feel about this topic:
“Fixing” defects is the developer’s job (exclusively).
“Finding” bugs is the tester’s job (exclusively).
And it’s best if these 2 hemispheres are kept separate.
But does […]
This seems like a silly question. Obviously, developers need to make sure their builds are stable before sending them on to the testing team. So yes, developers must at least taste test their applications.
But what we’re really asking is whether developers should conduct rigorous testing, complete with defect reporting, debugging, and methodology selection […]
The division of labor couldn’t be clearer:
Quality assurance professionals are supposed to test and report bugs.
Software developers are supposed to build and fix code.
Getting a product ready for launch might require hundreds (or thousands) of back-and-forth exchanges to fix all defects. However, that’s how the industry is set up.
But what about those really minor […]
In a recent email exchange with a long-time Testuff user, we learned that he wasn’t using one of the main screens in our platform. In fact, he wasn’t even paying attention to that screen. After digging a little deeper, we discovered that several others were in the same boat.
This surprised us given […]
We all write code, even in a relatively short project, for quite a long time. It isn’t just the first few days/weeks (sometimes months…) of the main writing period, but rather also the additions down the road, the fixes, and the patches. This means that the code gets “dirty” with time, no matter how “clean […]
It happens. Change is inevitable – and in many cases – initially not welcomed.
Parisians abhorred the Eiffel Tower originally. Now it’s a symbolic icon of all that is French.
People hated Gmail’s threaded conversations. Now it’s one Gmail’s most popular features.
Universal suffrage was a tough sell. Now countries that disenfranchise […]
We’ve touched on this theme a bit in the past – whether or not testers should be involved in the software design process.
Our feelings are pretty straightforward (spoiler alert – the answer is “yes” they should be involved). But before we explain why and to what extent, let’s look at some of the pros […]