User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:184.108.40.206) Gecko/20070718 Fedora/220.127.116.11-1.fc7 Firefox/18.104.22.168 Build Identifier: 1.3 Suppose I am developing test cases using the New Case functionality. Generally speaking, there is a lot of repetition involved in writing test cases, particularly when shooting for good coverage. Let's face it, writing a comprehensive set of test cases is tedious, and becomes an exercise in cut and paste and tweak. Currently with the dojo editing stuff, if you try to be clever and use the back button to go back and re-edit and re-submit a modified test case, you find that most of the fields are reset to empty. So you end up having to enter all those values again. sigh. Another possibility is cloning a test case, but this is still less desirable than the back-button method: click clone twice, then scroll way down to get to the bits you care about, and you have to click on edit to open up the pre/action/results/post editing boxes. Really, this is reasonably workable. But, what would be ideal, and maximally efficient in my view, would be to emulate the "Remeber bug as bookmarkable template" functionality of bugzilla. This way I can set the 80% of fields which are always the same, create a template, and then just go to that pre-filled form to add the 20% of distinct content. For bonus points, have a configurable option that even reloads that bookmark after I click submit (similar to the "go to next bug in list after commit" feature of bugzilla). Reproducible: Always Steps to Reproduce: n/a
There is a template field provided on the Parameters page under Testopia. You can enter a template for the Action and Expected Results fields there that will appear for any new test case. As for the other fields, though there is not button for it, you can add summary and bug information to the URL and save it manually.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Fixed. The form will now remain if you click NO when asked "test case ### created, would you like to go there now?" allowing you to make changes and submit another test case.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.