Forum Discussion
I am a little hesitant to too come in on this thread, because as richie said "there's lots of different ways of doing this", and there is nothing wrong at all with the suggestions he's made and anything I say could end up just causing more confusion. Sorry if it does.
All I can do is say how I would approach this issue. When you describe your problem I immediately think of data driven testing, the following link is a good introduction to doing this in ReadyAPI:
https://support.smartbear.com/readyapi/docs/testing/data-driven/index.html
I personally would look at how your tests are structured, as Ready API provides various tools to implement data driven testing, like the DataSource Test Step which when paired with a DataSource Loop Test Step, allows you to iterate over a set of test steps repeatedly different sets of data within a single test case.
This brings me to my next point, I always consider that a Test Case should be a test that is independent and runnable on it's own, with no prerequisites. To do this I usually have within my project a "Common Library" test suite where I turn all of my common functionality into test cases (for example a "Login" test case), then within the actual standalone test cases make heavy use of the Run TestCase test step. Your Test Suite then just groups your independent test cases into logical groups for easy running and reporting.
Take a look at my posts in these threads, as I talk more about modularising and reusing test cases (particularly the first link):
As I mentioned at the start I hope this helps a bit and doesn't cause too much confusion.