We are growing number of test cases, and we are storing quite detailed log out put (which very often is helpful), but this results in having a complete log for one database for one version sum up to 60MB, and current history of test runs already occupies 11G. We should review debugging and logging options and:
review and logs (even with debug) to so there won't be duplicates and excessive strings without much value;
add "debug" option so by default only general output would be logged.
I decided to strip from the testng-results.xml all non-essential information (we only need run data to generate index page with pass/fail/times) which reduces ~25MB files to couple of KB (information is still present in generated HTML). This slashed space usage from 32G to 12G and also sped up subsequent generations as there is less XML data to parse.
We are growing number of test cases, and we are storing quite detailed log out put (which very often is helpful), but this results in having a complete log for one database for one version sum up to 60MB, and current history of test runs already occupies 11G. We should review debugging and logging options and:
review and logs (even with debug) to so there won't be duplicates and excessive strings without much value;
add "debug" option so by default only general output would be logged.