Software testing knowledge? 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.

Following on from getting your A-Team together, you now need to get them involved in every which way you can. Get team members involved in documenting the process, in the decision making for your projects, and encourage actively speaking up when they see problems or issues. Keeping the communication lines open with honest and frank discussion, and group involvement, is always going to be better than a dictatorship! Waterfall, Agile, Exploratory, Context-Driven… the list goes on. You need to decide – hopefully as a team – which methodology and which practices of that methodology fit your organisation.

The ultimate ebook for more than software testing basics: How would you like to have all the software testing knowledge you need in one comprehensive book? Whether you want to level up in the software test management field, or gain useful knowledge of the sector as a whole, A Test Manager’s Guide is the resource for you. 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. Find additional details on Astqb Ebook.

Bug summaries must be thorough. Most customers including your managers, developers, and peers will read the summary first when they review a bug. This is especially true when they have more bugs to review. The simple reason is that they don’t have enough time to go into details of every bug, so having a short and concise summary will surely help to grab an idea of what the problem is about and how important it is. You can have a short and concise summary by telling exactly what problem you found and in what condition. Use Test Maturity Model integration. The software industry does not operate in a zero-defect environment, and, arguably, it never will. In the face of this truism, numerous techniques to reduce the number and severity of defects in software have been developed, with the ultimate, albeit unobtainable, goal of defect elimination. Such optimistic thinking has led to significant improvements in software quality over the past decade, notwithstanding increased software complexity and customer demands.

Quarantine software testing advice of the day : As you are developing and testing, team members need to make sure they are capturing everything more religiously than they might do if working in the office. For a tester, they could normally just show someone else (e.g. a developer) what happened on their screen, but when you are Teletesting, that is harder to. Use screen capture tools (like a free google extension – SpiraCapture) to capture what you are doing and then save the results into a tool like SpiraTest so that you have a record of what you just did. Similarly, make sure you document any changes or questions about requirements as a comment in the requirement. If you are not sure what the requirement means, add a question as the comment. If you are worried you will forget to clarify, just add a task to the requirement so that it is not forgotten. Teams should err on the side of adding tasks as well as comments to make sure things are not lost. Also as mentioned in item 3. if you need to get clarity on something, it’s fine to use IM tools, but make sure the results from that discussion make it into the tool being used for the source of truth. Explore extra info at https://cania-consulting.com/.