One of my favourite Test Manager feature is the data and diagnostics that collects information during my test runs to pass on in any bugs I log or get attached to my test run. The action recording proves the test case steps were followed, they allow me to fast forward the test next time I run the test or iterations. It has eliminated the bug state “Cannot Reproduce” The time all this data collected saves me in dealing with just bugs is unlimited. Developers love it too, they can diagnose bugs in no time.
I wonder if this helps in reducing the affect of the bug fix breaking other code. Now that would be interesting to investigate. Next project I’ll have to investigate all Test Impact and track how many were due to code changes involved in a bug fix.
Now I am in year five of using Test Manager and Visual Studio data diagnostics and my test runs and bugs are adding up in quantity therefore my database is getting full of all these test attachments. Do I really need to store the test attachments from a project that is done and 9 months old. Maybe not. What can I do?
The Test Attachment Cleaner a command line power tool that accepts parameters to remove test attachments form the database. Here are some examples:
- Identify list of attachments taking up database space of more than 1 GB per attachment
- View/Delete IntelliTrace log files over a size of 500 MB
- View/Delete all Video log files with Test run creation date older than specific date with no active bugs
- View/Delete all TRX & COV log files for test runs that happened between 30 and 90 days in age & do not perform the Linked Bugs lookup query
- View/Delete all custom/user attachments over size of 5 MB with no active or resolved bugs on test runs between 2 dates
Find out more and download Test Attachment Cleaner
If you need to keep the test attachment data it can be stored remotely which is setup in the Test Plan properties, test settings.