| || |
What are "Requirements" good for?
recently I have started using TestDirector and can't see the point in entering requirements under the "Requirements" tab. This will basically reflect the same hierarchical structure defined under the "Test plan" tab. So, if something requires to be tested, then why not simply add an empty Test Plan to be completed, instead of entering it as a requirement and later as a test plan?
Please can someone explain to me what I'm missing
Re: What are "Requirements" good for?
Think "Test Requirements"....
Where do you define what tests need to be created based on your Business, Functional and Technical Requirements?