Unnecessary file repeat in logs.
Hello,
I am using TestComplete 8.2 here at work on a bank of 55 test machines, that continuously run ~4500 UI tests (|450 tests with an average of 10 child items each). While the software in general works very well, there are two severe issues with the logging mechanism. The second issue I can live with, and is most likely cause by the way we name each test item. However:
1- Unnecessarily repeated script files and images in each test log. In each test log, for each individual run, over 450KB of images, Javascripts and Flash widgets are copied in each target folder. This approach is a ridiculous waste of space. It makes deleting old logs extremely long and is quite a strange way of doing things. Instead all the shared content should be placed in one single shared folder and linked to from each output HTML file. That is why HTML was created in the first place. To give you an idea of the size of the problem, a single build's worth of logs is over 10GB in disk size. That is about 250MB wasted per test machine, per day. Realistically, each test log should be no more than about 10KB of XML, so a daily log for all 55 test machines should hover around 1.8GB if each test runs 8 times.
Thank you for your time and consideration.
Hugo Lalumiere
Dynacom Technologies Inc.
I am using TestComplete 8.2 here at work on a bank of 55 test machines, that continuously run ~4500 UI tests (|450 tests with an average of 10 child items each). While the software in general works very well, there are two severe issues with the logging mechanism. The second issue I can live with, and is most likely cause by the way we name each test item. However:
1- Unnecessarily repeated script files and images in each test log. In each test log, for each individual run, over 450KB of images, Javascripts and Flash widgets are copied in each target folder. This approach is a ridiculous waste of space. It makes deleting old logs extremely long and is quite a strange way of doing things. Instead all the shared content should be placed in one single shared folder and linked to from each output HTML file. That is why HTML was created in the first place. To give you an idea of the size of the problem, a single build's worth of logs is over 10GB in disk size. That is about 250MB wasted per test machine, per day. Realistically, each test log should be no more than about 10KB of XML, so a daily log for all 55 test machines should hover around 1.8GB if each test runs 8 times.
Thank you for your time and consideration.
Hugo Lalumiere
Dynacom Technologies Inc.
