This change is to prevent a round-trip request/response to Polarion every time one of the functions addTestStep, removeTestStep and updateTestStep is called. In case a mass change of Test Steps is required, it would take a lot of time to process and also would generate a lot of revisions for the Workitem in Polarion.
In order to prevent this, each one of the functions addTestStep, removeTestStep and updateTestStep has a new parameter that tells if the action should be cached or not, and a new function saveTestSteps must be called to update the Test Steps to Polarion in case there are any cached changes.
The new parameters are False by default so as not to break compatibility.
This change is to prevent a round-trip request/response to Polarion every time one of the functions
addTestStep
,removeTestStep
andupdateTestStep
is called. In case a mass change of Test Steps is required, it would take a lot of time to process and also would generate a lot of revisions for the Workitem in Polarion.In order to prevent this, each one of the functions
addTestStep
,removeTestStep
andupdateTestStep
has a new parameter that tells if the action should be cached or not, and a new functionsaveTestSteps
must be called to update the Test Steps to Polarion in case there are any cached changes.The new parameters are False by default so as not to break compatibility.