Join 34,000+ subscribers and receive articles from our
blog about software quality, testing, QA and security.

Best practices: Projects vs Sections vs Subsections


Hi everyone! First time poster here :slight_smile:

My question is how do people who are testing complex products divide projects, sections, and subsections? We originally planned to use a single project for our product, but now we’re wondering if different areas of the product need their own projects.

Would this limit out ability to create test runs that span multiple areas of the product (ie, multiple projects)? What are some of the best practices people have used to document complex products?

A little background:

Our startup is preparing to formalize our QA process, and we have basically decided to use TestRail. Up until now, our QA process has been basically ad hoc – work with our developers and product team, get a sense of what needs to be tested, put it through the paces, log tickets in Redmine, and repeat.

This works fine with a small team (3 devs, 1 QA lead, 1 product lead), but as we prepare to grow we need something documented and repeatable. Our product is very complex, and as we’ve started to write up test cases, we are realizing that some screens may end up with hundreds of test cases, and our product has a lot of screens :expressionless:


Hi Mike,

Welcome, and thanks for posting! In general, we would recommend organizing your TestRail projects by product in most cases, and we would recommend using a single test case repository for your project. This makes it easier to start new test runs, filter your test cases and navigate between your tests. From there, you can organize your sections and subsections by functional areas of the product. You would then use milestones to manage your releases/sprints, and test runs/plans to manage your actual test execution. Please note that depending on your use case, in some cases you may be able to consolidate many test cases into one using the Test Case (Steps) template. This template allows you to add multiple separate steps to a test case, where each step can be marked as pass/fail individually, which helps to determine the overall test case’s status.

Hope this helps!



It absolutely does – thanks for the response @mgarcia!