I’m just starting to try out testrails in anger and I’m pondering on how to use test plans as opposed to test runs.
I have a single project with several test suites. Each test suite has 50 or so test cases divided in a few sections.
I want to create what I think of test plans (e.g. quick and dirty test, full test, acceptance test) each of which would use a subset of test cases from one or more of the test suites.
I’m trying to decide whether these should be test runs or test plans. Obviously if they span multiple test suites they need to be plans. But suppose the above examples are all related to a single test suite. Am I better creating test runs and then re-running them each time I need to retest or do I create a test plan with a single test suite in it.
I guess the essence of the question is: is a test run = a test plan with one test suite or are there differences which make one preferable to the other.
Apologies if this isn’t clear.
Nigel