Rally Software

 View Only
  • 1.  How do I resolve concurrency issues when using WS API's for test case exection results

    Posted Feb 08, 2018 06:12 PM

    After executing our test automation we are sending the results into Rally.  Here are the steps that we are following:

    1)  Create new Test Set

    2)  Add Test Case to Test set - The test case already exists in a test folder

    3)  Query for the test case within the test set

    4)  Post the results to the testcase within the test set.

     

    The issue we are running into is in step 3 above.  Sometimes, when a read is done to find the test case in the test set, it is unable to find it and so the results cannot be posted. 

     

    We have actually adjusted the code so it attempts 4 times with a 20 second delay between the third and 4th attempt and there are still several where results cannot be posted to Rally.

     

    If anyone else has run into this issue and could provide guidance on a resolution that would be great.

     

    I didn't include code because the majority of times it works.  It is just on occasion (15 out of 170 tests) it fails to find the test case in the testset and so cannot post results.



  • 2.  Re: How do I resolve concurrency issues when using WS API's for test case exection results

    Posted Mar 09, 2018 07:00 AM

    morky01, Would this be the same as this post on Stackoverflow:

     

    rally - 'concurrency' error from service when trying to save a second task - Stack Overflow 

     

    Michael



  • 3.  Re: How do I resolve concurrency issues when using WS API's for test case exection results

    Posted Mar 09, 2018 11:26 AM

    ChristineE I'd probably follow up with support.  This seems like a defect in WSAPI to me.  Please feel free to mention this post for some context.  Sometimes we do see some cache sync lag between app servers, but nothing on the order of 20 seconds.  Are you using one of our rest toolkits?