Hi,
I don't know if I'm misunderstanding your issue - the object hierarchy within ReadyAPI! is project >> testsuite >> testcase.
So I rely on the testsuite object to sort/order related testcases together based on what I'm testing. I tend to think about this BEFORE I start creating the tests.
Typically during my analysis phase, I create a high level design test case spreadsheet with multiple worksheets - each worksheet equates to a feature that's being tested and each feature being tested I equate to a ReadyAPI! testsuite. Each row in the spreadsheet's worksheet I equate to a test case.....making it easy for someone else to review my high level test cases.
I've rambled on a bit there - everyone does it differently - you might have a test management tool which represents my high level design test case spreadsheet - but the short answer is - I use the TestSuite object to equate to a 'feature' being tested. There are no additional levels in the hierarchy I mentioned above (project >> testsuite >> testcase) like sub-testsuite which would allow you to have multiple levels.
Important to thing to note is that I think about the hierarchy during my analysis phase, rather than just plugging away in soapui/readyapi! first - makes the analysis phase a little more rigorous and gives you the advantage of not having to try and reorder the testsuites/testcases on the fly.
I don't know if I've helped at all - but that's the way I do it,
Cheers,
richie
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
