I am currently running a trial of testrail and have a couple of questions about project structure in particular.
I’m working on a fairly large product that has a few distinct types of use cases, so I set up 4 separate projects for these major areas of the product, but that leads to a few questions.
Milestones are common across the product. So version 1.1 will have new versions of two areas of the product, and introduce a new area/use-case. In testrail, a milestone is a product-level entity, so I’ve just named them the same. That seems ok, but even though all projects have a “Version X.1” milestone, there are issues with tracking.
I’d like to create top-level test plans that span projects, and that doesn’t seem possible. If I decide to keep this structure, is there any way to manage test plans that span projects? If not, can I at least let the teams manage their test cases/suites/plans at the project level, and create a custom view to integrate the project-level test plan progress?
The reason I’ve chosen this structure is that one project for the entire product seemed too granular. I’ll have 40 people in a few different geographies working in a few discrete areas of the product, and that seemed to be a natural logical division within testrail too. It mirrors our boundaries in issue tracking, source code control, other tools, etc.