Software test planning tips

ISTQB test manager book? We’ve covered many different types of software testing in our recent guide to software testing, as well as in many individual posts (check out our testing archives here). Beyond knowing the ins and outs of software testing, it’s helpful to learn from those who have traveled the path before you to learn from their mistakes and leverage the tips and tricks they’ve learned along the way (and graciously decided to share with the development world). That’s why we rounded up this list of software testing tools.

There are a lot of great staff out there and typically with testers I find attitude is everything! Sure, you can learn great technical skills but if your team members don’t have the right attitude or intuition for testing you will probably be out of luck. If you are lucky enough to have great Test Leads or Testers you will probably find they have the right attitude and social skills to deal diplomatically with people of all levels in all sorts of roles. JDI is always a good approach! Speaking of tester’s intuition, check out one of the earlier blogs in the series on using your intuition, Testing and Bad Smells: When to Investigate Potential Bugs. Thanks Penny for a great post!

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. As a young graduate I started looking for potential career opportunities and this eBook has shown me the beauty and complexity of the Test Manager profession from a theoretical standpoint. Read even more info at Test Management.

Always start with a product map. Early on in the project you should spend some time exploring the software, and try to model the features and requirements of the product. A graphical model (for example, a mind map) can provide a concise, easy-to-understand representation of the product, and the modeling process is likely to help you uncover features that you may not previously have been aware of. When testers start working on the project from the very beginning, they make sure that many errors are identified and eliminated even before the development phase. Getting testers involved from the start means you can eliminate many errors even before reaching the development stage. When testers start working on the project from the very beginning, they make sure that many errors are identified and eliminated even before the development phase. Writing test scripts, quality testers assist developers that can later use these scripts for making product creation easier. Thus, involving testers into work at the first stages of development has a range of advantages: helping the team to understand customers’ goals, saving a lot of time, minimizing expenses, and optimizing the approach to testing.

Quarantine software testing recommendation for today : Regardless of how you do the meetings, make sure you are tracking any dependencies and people feel free to use the chat threads to reply to someone’s standup message with suggestions or offers to resolve a roadblock or dependency… We have a weekly product meeting which is longer than our standup meetings. We discuss how the current sprints are going, are we on track to deliver the next release on schedule, and are there any impediments or issues that we need to discuss. During this meeting we review the planning board for the current release and current sprints. Traditionally we’d do this in our conference room using our projector and take notes live in Google docs and/or use the whiteboards for any discussion topics. Find additional info at cania-consulting.com.