I would like to know any best practices being followed to maintain the repository. we have DB and repository in seperate boxes. We have approximately 150 projects in our QC. During the execution, the screenshots are being attached for each and every step causing the repository size to increase to a very high and hence we are facing the space constraint in the repository box. Please let me know if any one faced the same issue. Even if not please update the best practices being followed if any. Thanks in Advance.
Re: Best Practices in maintaining the QC repository.
#1: Purge old runs.
#2: Reduce the number of screenshots you're taking and storing. Do you need to have 50 snapshots of the same screen in the same mode in the same build?
#3: Make sure your snapshots are .png to reduce size (compared to .bmp) and where ever possible taken using QC's built in snapshot tool, to reduce the area captured also (to further reduce file size).
I'm a big believer that screenshots are only valuable for pointing our defects and are near-useless as evidence of execution. Collecting them wastes time and space.
In the last 5 years the number of times an old screenshot has been valuable to a project I've worked on is .. ZERO.
I can imagine times where they would be valuable, but all I can say is that in my experience the benefit of having them is outweighed by the cost of collection.