Inflectra Customer Forums: Purging Old Test Runs (Thread) Just wondering if there are others out there that have experienced the same problem as me, and if so do you have a solution? We are now approaching the 3 million test run mark and would really appreciate a script to purge old runs. Manually deleting test runs is a pain to say the least and attempting to create a script is asking for trouble. I mentioned this to Inflectra a good while back and was told they were looking in to it as they have the same problem when running automated tests. Cheers. en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/issues-questions/2011.aspxthreadId=2011David Bentham (david.bentham@se.consafelogistics.com)Purging Old Test Runs Just wondering if there are others out there that have experienced the same problem as me, and if so do you have a solution? We are now approaching the 3 million test run mark and would really appreciate a script to purge old runs. Manually deleting test runs is a pain to say the least and attempting to create a script is asking for trouble. I mentioned this to Inflectra a good while back and was told they were looking in to it as they have the same problem when running automated tests. Cheers. Wed, 24 Apr 2019 14:24:29 -04002019-05-06T09:09:56-04:00/Support/Forum/spirateam/issues-questions/2011.aspxmessageId=3571Jim R (donotreply5@kronodesk.net) Hi One of the reasons why its tricky is that the execution status of the test cases, requirement, Hi One of the reasons why its tricky is that the execution status of the test cases, requirement, test sets, and releases is all derived from the test runs. If you purge a bunch of old test runs you may potentially set test cases back to Not Run. One idea we had is to delete all but the most recent test run that matches any specific unique combination of test set, test case, custom properties, release, etc. but then you have test configurations, so even that may not be correct anymore.... Regards Jim Tue, 30 Apr 2019 17:05:42 -04002019-04-30T17:05:42-04:00/Support/Forum/spirateam/issues-questions/2011.aspx#reply3571messageId=3573David Bentham (david.bentham@se.consafelogistics.com) Thanks for the response Jim, I understand its a tricky issue but none the less its not going to dis Thanks for the response Jim, I understand its a tricky issue but none the less its not going to dissapear and the longer your customers stay loyal the more will be wondering how to do this in a more efficient manner as data grows. In our own application weve adopted a background process approach for purging unwanted/deprecated records, the proces is highly parameterized and with the possibility to schedule. I think this would be a good approach even for Spira. Just my thoughts. /David Mon, 06 May 2019 09:09:55 -04002019-05-06T09:09:55-04:00/Support/Forum/spirateam/issues-questions/2011.aspx#reply3573