Werner
Occasional Contributor
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: Custom Fields not accessible within Test Cycle Viewer
Simply true. You may raise a ticket to Smartbear. I'm asking me for which reason you need it? I never missed it till now. When I want to change the test cases assigned to the test cycle I always remove all test cases from test cycle and then I add them newly and when adding newly there is possibility to filter also for custom fields.97Views1like0CommentsRe: Is there a way to parse through a testplan API request and get the test plan key?
I did it this way: Firts I sent the testplan create POST request, it returns the test plan key within the response text JSON string. Afterwards I sent the testrun (test cycle) create POST request using the test plan key as input value so that the testrun gets referenced within testplan.59Views1like0CommentsRe: How to lock a test cycle (mark a test cycle completed and no more allowed to be changed/executed)?
Hi Andy, I need locked test executions of all test cases assigned to the test cycle. It means for me: Not anymore changes allowed to result of execution of test cases by means of test step and test case status (FAILED/OK/BLOCKED, ...) as well as execution time. The test case content (description and all its fields) needs to be locked within the test cycle to that version which was used in execution of test cases within the cycle. Archiving the test case does not help me as I still need the test cases for further future new test cycle instances. In future new test cycle instances the test cases may have got enhanced within new versions of test cases for example. Archiving we normally use just instead of deleting test cases completely. Thanks for your help Andy! Werner983Views0likes1Comment