Month: April 2011

Part of an effective QA cycle depends on an efficient test management process. In this webinar we look at ways to allocate work to your team using Software Planner and the ways in which you can analyse how your QA cycle is progressing. Controlling time effectively will allow you to make the most of your resources, whilst a greater awareness of the test status will help you to meet your targets. With the right project management tools you can keep up to date on your project’s progress. As noted in previous webinars, Software Planner is able to keep track of many aspects of your testing artifacts, including your software requirements, test cases, and defect data. The project tools can be...

There are some interesting comparisons between Octopuses and Test Management. For starters did you know that an octopus doesn’t have eight arms? Turns out that it has six arms and two legs (How Many Arms Does an Octopus Have?). Either way that’s a lot of limbs to manage. The management of the test process presents most of us with a similar challenge. The concepts behind test management are simple. Think up a test case, define the steps, write down the expected results, execute and log the result. It all boils down to this. The larger the product we’re testing the more we need to create. You couldn’t wish for simpler foundation. Simple is great, especially in the software development arena...

In this test management webinar recording we look at how to schedule automated tests to run daily during the QA cycle. Automating the execution of your testing and tracking those results in conjunction with your manual test efforts is key to maximising your resources. Integrating this process into an automated build process brings even more benefits with initiation of the automation coming from the completion of the build. With effective reporting and dashboards you can push back on development teams that deliver poorly unit tested builds to your QA team. Taking this approach is a good way to free up your team to concentrate on what is really important; usually the testing of new features not undertaking the unit testing...