In a Test Plan, the Features to be Tested and the Features not to be tested are generally included, is there any rationale behind why this should be or should not be included in a Test Plan?

Questions by nutankattapuram   answers by nutankattapuram

Showing Answers 1 - 12 of 12 Answers

shanti

  • Jan 23rd, 2007
 

some test cases(features) or not related to that particular build or release. They consider those test cases to be implemented and released in next build in for this purpose they specify those features in the features to be tested list.Correct me if I am wrongThanksShanti

  Was this answer useful?  Yes

nutankattapuram

  • Jan 24th, 2007
 

Thanks for the reply Shanti, but isnt a Test Plan prepared for the entire STLC? It is not prepared for each build. It is assumed that all the features listed in the Test Plan will be tested in some build or the other. I am enquiring about the Features in the Test Plan and not the test cases.

  Was this answer useful?  Yes

Bhargavi

  • Jan 24th, 2007
 

Every release will have a Scope. There will be some areas which will not be covered in the present build. So it is mentioned in the Test Plan that test cases which will cover those areas will not be tested. This will ease the test case preparation and avoid unnecessary work

  Was this answer useful?  Yes

kurtz182

  • Dec 2nd, 2009
 

The 'Features to be Tested' and the 'Feature not to be tested' are included in the Test Plan for the following reasons:

PRIMARY REASON
A Test Plan is typically reviewed by all relevant stakeholders in the company.  So adding the 'Features to be Tested' and 'Features not to be Tested' is a good idea because it allows these stakeholders to improve your test effort.  During the Test Plan Review, all stakeholders have opportunities to provide feedback and if features are missed or if features you intend to test can't be tested, these details will likely be brought up in this review. 

SECONDARY REASON
Consider what would happen if something goes drastically wrong in production because the test team failed to test some important functionality.  If this functionality was included in the Test Plan's 'Features not to be Tested,' and if all stakeholders signed off on it, then the test team can not be held responsible for the oversight.  I do not suggest we point fingers here.  Instead, there is obviously a great deal of improvement that can be made in the Test Plan Review process.   

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions