Hi, I've been using 1.6 for about a year now, and have created a very complex master Test Case system that we use to drive test plans for individual projects and releases. My work flow has been:
A: Define Keywords for coverage (modify those existing ones to fit our scope)
B: Create test case for Product (on going and always adding so there is never a 'finished set since our product line is extremely complex and there are just two of us creating cases)
C: Create test Plan for specific Project / with build management / adding cases based off keywords
D: Run Test plan / Execute and record cases (which in the past locked a copy of the case at the point you added it to the Plan and display that for the test execution, but I could continue editing/adding additional information or steps or permutations as uncovered for future runs for the test case within the master repository)
E: Work on test cases (modify, update, change, add more details) without having a lot of overhead of 'spawning a new version' for each individual bug.
Now, Any executed test case in 1.7, the only way to modify/update/alter or change after it has been assigned to a plan, is to spin a version. This is a lot of overhead if someone has a master test case repository that the cases can be used for patches as well as full releases which may be at the same time.
I can't find any functionality to 'release' an entire set of cases that have been executed during any test plan to continue work on the cases.
Is there functionality like this and I am just not seeing it, or each case that is executed will always be locked until you spin a new version individually if you want to edit the case?
Editing executed test cases under 1.7
Sure thing that solved my needs exactly. Thanksfman wrote:We have added a new config option, to allow you editing of executed test cases:
// 1 -> user can edit executed tc versions
// 0 -> editing of executed tc versions is blocked. [STANDARD BEHAVIOUR]
$g_testcase_cfg->can_edit_executed=0;
can this solve your problem ?