What is your special reason for more history? The number of history is 50 now, that means you can view the last 50 builds for each test, it should be enough.
The reason why we don't want to save too much history is that we think those elder test runnings may mean nothing, as in a daily development, we care more about those latest runnings. Also, the more history we stored, the larger the database becomes. So it will cause the insert/query to database slower. For example, if you have 1000 tests, and to store the last 50 runs, the data will be 1000 * 50 = 50000.
So, let me know why 50 runs for each test still cannot meet your requirements.
Steve Luo[04/Mar/13 11:45 AM]
What is your special reason for more history? The number of history is 50 now, that means you can view the last 50 builds for each test, it should be enough.
The reason why we don't want to save too much history is that we think those elder test runnings may mean nothing, as in a daily development, we care more about those latest runnings. Also, the more history we stored, the larger the database becomes. So it will cause the insert/query to database slower. For example, if you have 1000 tests, and to store the last 50 runs, the data will be 1000 * 50 = 50000.
So, let me know why 50 runs for each test still cannot meet your requirements.
Raanan Catz[04/Mar/13 10:03 AM]
Hi,
Does it possible to make the number of tests configurable? Maybe by add "Configure" to "Junit report" in Administration plug-in screen.
Thanks!
The reason why we don't want to save too much history is that we think those elder test runnings may mean nothing, as in a daily development, we care more about those latest runnings. Also, the more history we stored, the larger the database becomes. So it will cause the insert/query to database slower. For example, if you have 1000 tests, and to store the last 50 runs, the data will be 1000 * 50 = 50000.
So, let me know why 50 runs for each test still cannot meet your requirements.