Test management eBook
ISTQB book? 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.
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.
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 a few more details on Test Planning.
Develop rules of thumb – and document them. As testers, we often use rules of thumb throughout a project. For example, we sometimes use a total number of expected defects during test planning and then compare actual defects per hour found versus what we would expect, during test execution. Each of these rules of thumb aids us in managing the information we deal with as testers and QA managers. It would be nice (and useful) to have a collection of these rules of thumb in one place, each documented with examples. Conduct code reviews. Four eyes see more than two. That’s why you should let other developers review your source code on a regular basis. Pair programming, on the other hand, a technique where two developers write code together for longer periods, isn’t for everyone and is often not needed. But complicated, important or security related code greatly benefits from code reviews and will improve your code quality a lot.
Isolation software testing tip of the day : 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. Explore even more info on cania-consulting.com.