Software test planning guide? Treat testing like a team effort. “Testing is a team effort. You’ll find keeping everyone in the loop from the beginning will save an enormous amount of time down the line. “When you expose testers to a greater amount of the project, they will feel much more comfortable and confident in what their goals should be. A tester is only as efficient as their team. “Your goal is to make sure everyone involved in the project has a solid understanding of the application. When everyone understands what the application entails, testers can effectively cover the test cases.
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.
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 on 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 more details at Test Manager Ebook.
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.
Work from home software testing tip for today : Perhaps there are other things that you can automate (support chat bots, performance monitoring) that previously the team did manually but are not so ideal for distributed teams. Computers can work day and night and don’t worry about spreading viruses (or at least not that kind!!) so automation is a good approach for any tasks that it’s feasible for. It’s easy to forget the people and focus on the product, but the move to 100% telework, especially when there is a wider national disaster (like the current Coronavirus) can actually make things worse – people have more time to read the news, check social media (twitter) and generally get stressed out. The good thing is that having work to do keeps people’s mind off the wider picture, but balancing family/home/work time can be stressful. See more details at cania-consulting.com.