jesper-raemaekers / python-polarion

A Python package to access the Polarion WSDL API.
MIT License
54 stars 34 forks source link

Update record #169

Closed iosu1998 closed 2 months ago

iosu1998 commented 4 months ago

Hello,

I'm trying to update the record results and I've just realized that, even for each step, a "retest comment" label is added even for each step.

Debbuging, I've reached the conclusion that it's because of the Record Save method, which is using the ExecuteTest wsdl and it's used in both setStepResult and setResult.

Whenever I update the results I update both. That's why just having the save in the setResult will suit me.

Also, would be interesting to use the wsdl method UpdateTestRecord or UpdateTestRecordAtIndex.

The comparison between this two methods and the previous one, according to the web service, is the following:

So, with the second one, results could be updated in the way the user wants to, I think that could be interesting to apply it, in order to modify already uploaded record.

Also, I didn't see any manual way to delete records from Polarion manually.

I don't know which is the best way to do this. In my case just the comment and the result fields are interesting to be changed, but I guess I should implement also the other ones and I don't know which is the best way to do it. In my case I'm copying the record, doing the same as it's done in the Save method to fill the new item and afterwards modifying the comment and the result to fit the new ones.

I can try doing something and then modify my changes and let it properly.

Thank you.

nunobrum commented 4 months ago

I implemented in my clone repository a dedicated class for managing test records. It doesn't solve everything but it's more efficient and easy to use. I tried to pull-request it back to origin, but it's tricky to maintain backward compatibility.

iosu1998 commented 4 months ago

That's why I asked. I could apply the things I need by myself. However, making the changes here It's easier for me to maintain the code and to keep those changes in future releases. But the backward compatibility could be difficult in this case

github-actions[bot] commented 3 months ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 2 months ago

This issue was closed because it has been inactive for 14 days since being marked as stale.