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 loads of Test Management Tools out there at the moment. As mentioned previously, metrics and reporting are made all the more difficult if you don’t have one implemented. The tools out there at the moment vary wildly in price. You can get some relatively cheap tools (or very expensive if you prefer) that are actually usable and give you the ability to store your scripts in one repository, collect metrics, and provide reporting. It is well worth a look at least… (FYI – this information is coming to you from a Test Management Tool convert!).
If you’d like to step up your skills from the software testing basics, and access some of the best insider knowledge in the industry, this ebook is for you. A Test Manager’s Guide will make an essential addition to your collection as you continue to develop within this field. 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. Explore even more info at Cania.
Find out what the software under test is not expected to be doing. Try those things out. The ‘what if’ should become the leading question of the software research. So you are finding yourself in the middle of Apple Watch testing. How will it act if an iPhone it is paired to runs out of battery, etc.? If you can do anything in the system (meaning it allows you to), do so without question and despite everything telling you shan’t do just that. If possible, get the system (or device) under test out of your working premises and try it in a real environment. Don’t rely solely on written communication, particularly for virtual teams. Especially in virtual teams often the only point of interaction between developers and testers are bug tracking system, yet it is especially the written word that causes misunderstandings and leads to pointless extra work. Regular calls and actually talking to each other can work miracles here.
Isolation software testing recommendation for today : For those who are not used to remote working, it sounds idyllic until your dog/kid/partner starts driving you up the wall. And remember we are not at home because we want to be. We should do what we can to make this easier for each other, and look out for each other. Sending care packages can be a good idea, as long as they don’t get in the way of essential supplies being delivered (at the time of writing this article, Amazon is rumoured to have started delaying non essential shipments). Leaders in the company need to let people know that the company is OK with productivity taking a dip overall. Also there will be a tendency for people to use the company’s channels (instant messengers, virtual meetings) to discuss things in the news and compensate for their relative isolation. Leaders should tolerate and encourage this. Expect that most company meetings will start with 10 minutes of banter unrelated to work, that’s OK. See a few more details on cania-consulting.com.