Actions
Forum Thread Details
  • State Not Answered
  • Replies 2 replies
  • Subscribers 350 subscribers
  • Views 288 views
  • Users 0 members are here
Related

How much time should be dedicated to scenario planning when developing a Test Plan?

Tom@Bbite

How much time should be dedicated to scenario planning when developing a test plan?

 

The  effort required  for preparing a Test Plan depends on test equipment  availability, structure but also in Testing knowledge. If you are well  versed in Test then  it obviously saves time and the final copy of the  plan can be drafted  quickly. The same applies for the effort required  for Test scenarios and  creation of Test Cases. However, if you are  relatively new to the system under test and  environment then more time  will be consumed but there is  no fixed rule/formulas for figuring out  the effort for any testing  activity.

Unless the scope of the testing activity is  finalised, the Test plan document version count might well increase.

What % of time is allocated to Test Scenarios in teh overall scheme, or what should be allocated?

1.Testplan - 10%?

2.Test scenarios - 30%?

3.Test Cases - 60%?

  • 0

    Test Scenarios and Test Case mean the same thing when working on a test plan. Test scenarios are test cases with the sequence they will be executed.

     

    I say 60% is a good number. Drop the 30% in step 2. Now you have some extra time to add elsewhere.

     

    E

  • 0

    Hi Tom,

     

    A test plan covers two aspects of the product.  Does the product meet its requirements and can the product be used as specified.

    You need a test scenario for each separate feature or option provided by the product.

    You need Test Cases to verify the specific requirements needed to implement each feature.

     

    So where do you spend the time?  It depends upon the number of features and unique test cases needed for the requirements.  This last point is key.  You can test multiple requirements with a given test scenario, so you need to make a quick matrix to show that the scenarios you have chosen cover the key requirements.  Sometimes you can negotiate the level of requirements to be tested, but for most products, you need to test them all.

     

    I usually would take my requirements breakdown from the Requirements Analysis process and then map tests to that matrix.  That is the quickest way to scope out your test effort, identify the test equipment and the accuracy needed for each measurement.  Remember, if you can't measure it, it is not a requirement, it is a demonstrated function.  Try to get most of the user features into the demonstration category.  Only measure what can be definded with quantitative numbers.  Fast as it can is not a testable requirement.

     

    Ideally, you build the test plan as you analyze your requirements.  If you have a separate test group, get them involved with the requirements analysis process, it will save you a lot of time and effort later.  If you are the Analyst, Designer, Builder and Tester, then you have complete control, but you need to take the time to view the job from each separate perspective.

     

    Bottom line, your requirements will dictate where you should spend your time on the test plan.  I have been on many projects where the Test Scenarios were more important than the actual test case measurements.  On others, we spent all of the time verifying measurements.  So each project can be quite different.

     

    I hope this helps,

    DAB