Test case documentation structure
My company is moving to VSTS and reorganizing our test case documentation structure in the process. We are moving towards a documentation numbering structure that links test case items to requirement & sub requirement line items.
Parts of our application set are web based - so a given requirement needs to be tested on a variety of platforms and browsers. Other parts are low level hardware based so the testing platform requirements are extensive - laptop model and OS are relevant for each test case. Correct test results may vary depending on the laptop model and OS.
I am looking for an efficient way to structure the test case documents in VSTS. My goal is to have the primary organization of the documents to be requirements based - by requirement / sub requriement number.
My problem is how to efficiently structure the extensive platform based test cases & results within the requirements based structure.
Does anyone have experience with this problem?