Software Test Design and Planning news, help and research - SearchSoftwareQuality.com

Software Test Design and Planning

  • Streamlining user acceptance testing (UAT) with Agile

    Organizations that implement successful user acceptance testing can greatly reduce errors and business risks.  Tip

  • ALM: Managing offshore test teams

    This tip emphasizes expressing clear expectations throughout the application life cycle. Learn how to choose the most effective means of communication for the situation, how to motivate team members across the miles and how to show appreciation to of...  Tip

  • Automation testing: Seven tips for functional test design

    In this tip, Chris McMahon describes seven tips for testing leaders that will ensure you are designing your automation tests correctly so that they will be maintainable and catch the bugs before the code hits production.  Tip

  • Code coverage: Beyond the basics

    Code coverage tools will tell you how much of your code has been executed when you run your tests, but what can we do with that information? In this second of a two-part series, consultant Mike Kelly explores code coverage more deeply.  Tip

  • How useful is code coverage?

    In this first of a two-part series about code coverage, software consultant Mike Kelly explains code coverage and gives a specific example of how code coverage was calculated on a small program using the tool rcov for Ruby.  Tip

  • Tips for interpreting JMeter results

    Interpretation of results from performance test tools is complicated. Learn how to interpret data from your JMeter Listeners using scatter charts, and by using the Aggregate Report Listener and the Monitor Results Listener.  Tip

  • Mobility testing: Five challenges and how to address them

    Smart phones and other mobility devices continue to grow, as do challenges with mobile testing. This tip addresses each of these challenges with advice on how to best overcome them.  Tip

  • Software testing from the ground up

    Where do you start when asked to test software? In this tip, SSQ contributor Matt Heusser talks about the tutorial he is delivering at STPCon with Pete Walen about software testing from the ground up. Learn about quick attacks, domain analysis and kn...  Tip

  • Software testing: Why test metrics programs fail

    “Most testing metrics are internally focused, and this is one of the primary reasons for these programs to fail,” says Infosys leader Vasudeva Naidu. In this tip, Naidu describes this and other issues and gives four golden rules of testing metrics ma...  Tip

  • Mobile Web applications: Monitoring test triggers

    Learn how to build out a system for monitoring test triggers for mobile Web application and its supporting systems.  Tip

  • See More: Tips on Software Test Design and Planning

  • gray box

    A gray box is a device, program or system whose workings are partially understood. Gray box testing, also called gray box analysis, is a strategy for software debugging based on limited knowledge of the internal details of the program. The tester may...  Word

  • PERT chart (Program Evaluation Review Technique)

    A PERT chart is a project management tool used to schedule, organize, and coordinate tasks within a project.  Word

About Software Test Design and Planning

Test design and planning is the process of determining what types of testing will be performed and then designing the test cases. Depending on the functionality of the application, test design and planning will need to consider which test tools available, skills of the team, and overall complexity and project high-risk areas. Test design and planning requires the prioritization of test cases, determining when test cases will be executed throughout the cycle, estimating effort, time, and cost, and defining the criteria necessary to consider test complete.