With the basic understanding that we can’t test everything, we need to decide what are we going to test. This is where risk-based testing enters the picture.
Tag Archives | Testing Intelligence
Leading By Example
*The following is a guest post by Brendan Connolly, SDET at Agilysys. The opinions stated in this post are his own. Testers, even when embedded on teams, end up being outsiders. Their value is derived from, maintained by, and is continually put at risk by this status. In the early days of software development there was […]
Testing Under Stress
Dealing with the stressful reality of testing in today’s fast paced development cycles Our lives are full of stress both at work and at home. Is seems at times that there aren’t enough hours in the day, and everyone around us has their demands for our time, which is forever limited. Working in the current […]
Your next testing progress report
Next time you give a progress report think about what is the important information you want to communicate to your project team. Here is a list of examples of things we usually forget to add to our reports…
State of testing – summary post
For the first time ever on a global scale a State of Testing survey was conducted to get a snapshot of the current state of the testing community, it’s members profiles, professional challenges and work practices worldwide. PractiTest in cooperation with Tea Time with Testers came up with the State of Testing survey with the intention to […]
C’mon!! If you have something to say, get up and say it!
Following up on a comment left on a previous blog post, I wanted to explain why should testers provide their feedback regarding the priority (and not only the severity!) of bugs. The post also explains what are the ways of making sure this opinion is heard by the whole team.