Hi everyone! First time poster here
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