Subscribe Join 180,000+ subscribers and receive articles from our blog about software quality, testing, QA and security. Subscribe

Deleting test runs via api is timing out


I am trying to delete alot of old closed test runs via the API, and it seems eventually the api requests will start to time out. I tried to re-issue the delete request for the test run id that timed out, but it reports that it is no longer valid, so I am assuming that it was deleted from the runs table. Could the request be timing out deleting the cases/tests that are associated to the test run? Does the run get deleted first, and then the cases/tests data is deleted afterwards? Am I safe to continue on deleting other test runs when I hit one of these timeouts?