Test management book? The list features tips and insights from experts on many of the less black-and-white aspects of testing. Such as considerations for choosing the right tests, creating a testing culture that sets the stage for successful testing among teams, prepping for tests, testing with greater efficiency, and other important insights to streamline your testing process and get better results in less time and, often, at a more affordable cost.
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.
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. Find a few more info on Cania.
Opening up the communication lines between the testing teams can do wonders for making the testing smooth. Keep open lines of communication between testing teams. Opening up the communication lines between the testing teams can do wonders for making the testing smooth. Communications allow the team to compare results and share effective solutions to problems faced during the test. This will also ensure clear assignment of each task. All members of the team should get updated with the current status of the test. Automation is good, but it doesn’t fix poor test design. Test design must take into consideration all the areas of testing to be performed, but it should also identify high-risk areas or other specific areas where test automation would add the most value rather than leaving such decisions to be made ad hoc once development is in later stages.
Quarantine software testing trick of the day : We recommend that you choose a very, very small number of apps that are your source of truth – so everyone knows where to go to see what they and others need to do. For example we are using SpiraPlan as our sole source of truth of product development and testing tasks. We use: Tasks for development activities, Incidents for any bugs to be fixed, test Sets for any assigned tests to be run. With requirements and releases/sprints being used to roll-up the information to see what needs to be done across multiple tasks and test cases. We have a rule that anything that is in Google Chat or email is not by itself a task, to avoid confusion about priorities. If you want me to remember to do it after the next 5 minutes, don’t put it in Chat or Spira instant messenger. Chat is only for immediate questions/responses, not task assignment. For other, non-development teams, there should be an equivalent source of truth (CRM activities log for sales, KronoDesk support tickets for support, etc.) Read extra info at cania-consulting.com.