I am in the process of writing test cases based on system use cases and need some insight on documentation. Is there a RUP template for documenting test cases that span across more than one use case?
Creating test cases based on a single use case seems to create an isolated set of tests. For instance, I have a use case named Navigate Map which consists of several scenarios: Zoom In, Zoom Out, Pan, Zoom to Active Layer, Zoom to Previous Extent, etc. Creating test cases for the scenarios only tests map navigation. I have another use case named Query Facility. The purpose of this use case is to provide the crew the ability to query and locate water or waste water facilities (underground infrastructure. A test case that queries a facility and once found a tester selects to zoom out or zoom to previous extent which ensures the two functions work together seems to be beneficial. What is the best way to the document the test cases so they span across several different use cases to show better testing as oppose to isolated function tests? **************************************************** J Williams EMA, Inc. "Linking People & Technology for Business Results" ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Post or Reply to: [EMAIL PROTECTED] * Subscription Requests: [EMAIL PROTECTED] * Archive of messages: * http://www.rational.com/support/usergroups/rose/rose_forum.jsp * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * To: [EMAIL PROTECTED] * Subject: <BLANK> * Body: unsubscribe rose_forum *************************************************************************
