Key: |
QB-1488
|
Type: |
Improvement
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Steve Luo
|
Reporter: |
shani hayoun
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 26/Dec/12 12:02 PM
Updated: 04/Mar/13 11:45 AM
|
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
5.0.3
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
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.