Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-1266

Create stress test for REST API with coverage of all methods and abort code paths.

    Details

      Description

      This is in response to BLZG-1236 and similar issues that have appeared in the past. We need to establish better code coverage over the REST API when using non-standard code paths involved with abort handling followed by successful commits.

        Issue Links

          Activity

          Hide
          bryanthompson bryanthompson added a comment -

          Substantial work has already been done on this in the StressTestConcurrentRestApiRequests class in the TICKET_1156d branch. Much of this is documented on other REST API tickets.

          Show
          bryanthompson bryanthompson added a comment - Substantial work has already been done on this in the StressTestConcurrentRestApiRequests class in the TICKET_1156d branch. Much of this is documented on other REST API tickets.
          Hide
          bryanthompson bryanthompson added a comment -

          http://github.com/SYSTAP/bigdata/pull/73 was merged to master.

          I have conditionally disabled the REST API stress test due to the stochastic "namespace: EXISTS" test harness error in the master.

          I have created a new branch (TICKET_1156d) for continued work on the REST API (client and server).

          We need to coordinate work on BLZG-1126 and BLZG-1136. We should at ways to share a common execution layer. This is critical in terms of correctness (especially of error handling logic and group commit behaviors) and test coverage of the various methods.

          Show
          bryanthompson bryanthompson added a comment - http://github.com/SYSTAP/bigdata/pull/73 was merged to master. I have conditionally disabled the REST API stress test due to the stochastic "namespace: EXISTS" test harness error in the master. I have created a new branch (TICKET_1156d) for continued work on the REST API (client and server). We need to coordinate work on BLZG-1126 and BLZG-1136 . We should at ways to share a common execution layer. This is critical in terms of correctness (especially of error handling logic and group commit behaviors) and test coverage of the various methods.
          Hide
          bryanthompson bryanthompson added a comment -

          Igor, I've moved this one into the next release.
          Thanks,
          Bryan

          Show
          bryanthompson bryanthompson added a comment - Igor, I've moved this one into the next release. Thanks, Bryan

            People

            • Assignee:
              igorkim igorkim
              Reporter:
              bryanthompson bryanthompson
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: