Adding attachments to testruns

[Dineshkumar-Ponnusamy]

Describe the bug
Currently adding the attachments based on items didn't work for the test runs.

To Reproduce
Steps to reproduce the behavior:

1. Create a test plan
2. Create a test cycle
3. Create a test run
4. Upload documents/images
5. Try to attach the items to the test run

Expected behavior
Attachment should be uploaded to the corresponding test run.

Desktop (please complete the following information):

• OS: Windows
• Browser: N/A API request

Additional context

1. https://community.jamasoftware.com/communities/community-home/digestviewer/viewthread?MessageKey=f99f95dc-9f2e-4a57-b116-2b002d5cc7db - Attachments in Test Run
2. https://community.jamasoftware.com/communities/community-home/digestviewer/viewthread?GroupId=25&MessageKey=de0bdf91-8867-4036-b29e-3f37adf0a0cb&CommunityKey=c9d20d4c-5bb6-4f19-92eb-e7cee0942d51&tab=digestviewer - Upload attachements in Test Run using Python

[JKMicroP]

I ran into this very issue. The problem is that post_item_attachment wil try to attach the attachment here: <jama_URL>/items/<id>/attachement
while the test runs (at least for me) is here:
<jama_URL>/testruns/<id>/attachement

I would suggest adding a new function "post_testrun_attachment" to the jama client which will do exactly the same as post_item_attachment but aim at the testruns path instead.

Workaround could include adding an argument to post_item_attachment with a bool "test_run = False", and then an if statement selecting the appropriate path.

That is not ideal for my situation since patching the jama client will mean that i need it patch on any work station that will run our test frameworks.

Other workaround (which I have yet to test) would be to create a post_testrun_attachment in my normal test framework and not use the jama client.