Software Test Strategy For Time-Pressured Projects

The proper testing of software takes a lot of work, and therefor a lot of time. While I don’t agree with this tactic, when projects get delayed, the time to test the system is one of the most likely candidates to take a hit when squeezing the schedule. "Two weeks delayed? We test two weeks shorter, and presto, back on schedule again."

When facing a short time frame available for testing purposes, you got to make the best the time and resources available. A software test strategy that takes this into account is risk and requirements based testing.

In this strategy we assume that it’s undoable to test everything. From a economic point of view it doesn’t even make sense; spending lots of time to parts of a system where the changes of having a bug are low, or even if a bug has been found, where the impact of it will be low. Risk and requirents based testing helps you to determine what to test first, in which sequence, so you spend the time you have to the parts that really matter.

The strategy starts with a risk analysis to determine the functions (requirements) with the highest risk, and plan your test activities guided by this analysis.

To help you identify the risks involved in all your requirements, consider the following aspects:

  • Functions often used by the users

  • Complex functions

  • Functions that have a lot of updates or bugfixes

  • Functions that require high availibility

  • Functions that require a consistent level of performance

  • Functions that are developed with new tools

  • Functions that require interfacing with external systems

  • Functions with requirements with a low level of quality

  • Functions developed by more programmers at the same time

  • New functions

  • Functions developed under extreme time pressure

  • Functions that are most important to the stakeholders

  • Functions that reflect a complex business process
Share on Google Plus

About Debasis Pradhan

Debasis has over a decade worth of exclusive experience in the field of Software Quality Assurance, Software Development and Testing. He writes here to share some of his interesting experiences with fellow testers.


Post a Comment

NOTE: Comments posted on Software Testing Tricks are moderated and will be approved only if they are on-topic. Please avoid comments with spammy URLs. Having trouble leaving comments? Contact Me!