ASTQB guide? Most experienced developers understand that software testing isn’t a singular approach, although, in the broadest sense, it refers to a collection of tests and evaluations that aim to determine whether a software application works as it should and if it can be expected to continue working as it should in real-world use scenarios. Basically, software testing aims to ensure that all the gears are churning smoothly and work together like a well-oiled machine.
What metrics do you want? The one size fits all approach just doesn’t work for collecting metrics. It depends on so many factors and unless you are using a Test Management Tool of some description you are unlikely to have all the stats you need at hand. As a starting point you need to understand what the key factors are that mean most to you. Do you have a drop dead date for your projects? Do you need your requirements to be exact? Do you need your estimation to be near perfect? Once you work out what is critical to you and your organisation, start collecting the metrics for this. Focus the collected metrics around your key factors and this will help you get what you need without creating a significant overhead in collecting all other metrics.
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. 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. See additional details on Test Management.
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 advice 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. Explore more details on https://cania-consulting.com/.