Interesting Things Blog Education Software test management tricks

Software test management tricks

Test management eBook? 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. 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. Discover extra details at Test Management.

Report findings in the context of business value. Focus on the data that is being communicated back to stakeholders, from your findings as part of testing – the data should be in context of ‘how’ the behavior observed is detrimental to the objective of the feature or application being developed. Engage the end user. Probably the most important person in the whole process, yet many times we may be tempted to keep them at arm’s length; you should involve the customer actively. Have them give frequent feedback on the product for future improvement and development; software developers who respond quickly to customer feedback are generally more successful. Always keep learning. [The] IT field changes; way [faster] than some of us would like. If you are not constantly updating your skills, you could get irrelevant, obsolete and outdated. In a world of lay-off paranoia, it is a good idea to rise above it all, gain immunity and feel secure. The best way to do so is to make learning a habit.

Work from home software testing recommendation 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. Find additional info on