| || |
Testing Estimates for SW Upgrade without Requirements
Does anyone have any advice, templates, ideas on how to provide an extentsive estimate when there are not requirements. The requirement is to TEST EVERYTHING, because its a software upgrade.
Thanks in advance for responses.
build a risk based test matrix and provide effort for each component testing. Testing provide the snapshot of current level of confidence. Whatever risk you will cover , provide the same level of confidence. Keep the level you want to go out of door in exit criteria in Test Plan.
You can explorer this link:
Risk Assessment: Creating a Risk Matrix
There are always requirements, even if they aren't written down.
This might help your thought and estimation process:
All Things Quality: There are ALWAYS Requirements
If your real "Requirement" is simply to "Test Everything", you must first determine what "Everything" is.
Then break down "Everything" into reasonably-sized, better understood, and more easily estimatable components/chunks.
Estimate the testing effort for each component.
When you say that it's a "software upgrade", does that mean the application-under-test itself has been upgraded? Or just the underlying operating system? If the former, you probably have new/changed features that probably have some sort of written indication as to what changed. If the latter, the expectation may be that nothing at all in the application-under-test is expected to change.
One thing that may help you here is that you may have a handy "oracle" available to you - the currently running production version of the application. You can use it to help you understand what "test everything" actually means. And you can use it as the basis of "correct behavior". If you set up a test environment containing the same data as the Production version, you may be able to perform the same action on both the Test and Production versions, and expect that the same results will occur. Explore a little and find out if this is the case - it could greatly reduce your testing estimate.
Last edited by Joe Strazzere; 05-28-2013 at 04:11 AM.