As a manager, it would be extremely useful to have a collaborative communications workflow that centered on the development of test cases within TestRail. For example at my organization, we use our engineering issue tracker (Trac) to handle the collaborative “development” of test cases, which means when test cases are being devised or adjusted, I/we have to constantly jump between Trac and TestRail (or sometimes on a Google doc) until a case/section/suite is up to my/our standards.
For us, it would be extremely beneficial to be able to conduct this work directly in TestRail, by immensely streamlining the process of devising and maintaining test cases. Reports and APIs are great, but I think getting/keeping the test cases “right”, and the suites properly structured/organized is the first important step toward having a solid test coverage regime, so it would be great if TestRail could do more to help with this part of the process.
This feature would ideally include an expanded set of rules concerning who receives email notifications, and which events can trigger them. Additionally, similar to the commenting feature on test runs/results, it would be extremely useful (at least for us) to be able to enter comments on test cases themselves (which would be one event that could fire off an email).
For example, as I write this, I have before me a new suite of about 100 test cases organized into 12 sections that I need to review and provide feedback on for an upcoming release. I have commentary related to the organization of the suite/sections, as well as specific adjustments that are needed on individual test cases. I’ll have to now work in Trac, pasting links to relevant sections/cases in TestRail, and/or document my thoughts in the meandering Google doc we have set up for this, and/or schedule a meeting, in order to get this suite where it needs to be - which is inefficient (and a little painful) for all involved.
It would be oh so nice to just run through the suite in TestRail, commenting as needed, and know that the folks who needed to get them would receive a series of emails with marching orders spelled out (like my developers do with Trac for routine tasks).
If there’s already a way to accomplish this…or if folks think we’re just “doing it wrong”, please chime in with suggestions!