Software test manager guide? Encourage clarity in bug reporting. “Reporting bugs and requesting more information can create unnecessary overhead. A good bug report can save time by avoiding miscommunication or the need for additional communication. Similarly, a bad bug report can lead to a quick dismissal by a developer. Both of these can create problems. “Anyone reporting bugs should always strive to create informative bug reports, but it’s just as important that developers go out of their way to communicate effectively as well. For instance, if a developer needs more information, it’s best if they take the time to write a detailed request. Teach people to write good reports, but hold your developers to high standards as well. If everyone is going above and beyond to communicate effectively, everyone’s productivity benefits.
My original comments on test estimation are as follows, “Arrrgh… test estimation. Get your team to get it right and you may have uncovered one of the mysteries of the world. Enough said.” Then I thought I better expand a bit… Your organisation has many unique factors that you need to take into account. The best form of estimate can be based on past test execution history – generally only available when you have previously collected metrics on test execution. Other than that you will need to have your team factor in as much as you can regarding areas such as environment, quality of resources, past test execution history, and technical difficulty.
Lucian Cania is an experienced international IT delivery and software test manager with a vast experience in test management. He founder Cania Consulting by leveraging a vast background in Transformation Programs executed across Europe in the areas of ERP, BI, Retail, Billing and Integration. After passing the ISTQB Foundation Certification, this eBook was great source to better understand what to expect from the Test Managers working on my Software Projects. Discover a few more details on Test Levels.
Rather than rely on traditional QA testing methods, Developers and development managers should also be able to quickly and easily manage the defects in their code – especially where code is complex. Manage defects in code during development, particularly for complex code. Rather than rely on traditional QA testing methods, Developers and development managers should also be able to quickly and easily manage the defects in their code – especially where code is complex. This includes prioritizing defects based upon impact and filtering defect information to view only what’s relevant to them. Once the defects have been prioritized, developers should be able to automatically find all of the places the defect exists across projects and code branches – thus minimizing duplication of efforts. Then they should be able to collaborate with other developers to share triage information across distributed teams and geographic boundaries.
Quarantine software testing trick of the day : Normally with agile teams it is ideal to have a daily standup meeting where everyone discusses what they are working on, identifies any roadblocks, and raise any team-wide issues that should be addressed. With the move to complete teleworking, we have used our normal team chat application (for us a combination of Google Chat and/or Spira instant messenger, but you can use Slack, Microsoft Teams, etc.) to write a new thread with a daily standup message each day: This was so successful that our sales and marketing team have followed suit with their own version! Its a good, quick medium that works with the immediacy of a standup and avoids long drawn out meetings that are the reason you “stand up”. We have also been experimenting with a virtual 15 minute Google hangout call. When we had the team partly colocated and partly teleworking this wasn’t necessary, but with people feeling socially isolated due to the wider quarantine conditions, hearing/seeing each other has been helpful. One team member also showed us his cats playing which was a nice morale boost! See extra details on cania-consulting.com.