I’ll start this off by saying I’m using test cases in TestRail, and politely request that the discussion doesn’t derail into talking about me dropping test cases or automating them, as that’s not an option for me, thank you.
My company’s product is large and somewhat complex; the most I can give away is that our software helps energy suppliers maintain their customer base, their meter readings, and their billing/invoicing.
I’m writing test cases for the separate areas, but some features need other parts to be set up in a specific way in order to test them. For example, selecting an option on a form at the start of the setup process changes the way meter readings can be obtained, which then have their own set of parameters that can generate an estimate reading, which then can change text in a results table to show one thing, or another. There are lots of other instances also, this one is just the first I’ve come across while writing test cases.
My problem is that I don’t know where to put these test cases. As the system is so large, I’m having to create different test suites for different parts of it, which has the potential to become messy. I have sections to make sure each individual feature functions as the requirements state, but haven’t got to the part where they need to work together.