MantisBT - TestLink
View Issue Details
0002132TestLinkReportspublic2009-02-20 07:072014-07-28 20:33
1.8 RC 4 
1.9.11 (2014 Q2 - bug fixing) 
0002132: testreport does not scale when high number of builds
We are planning for multiple builds per day with an automated process saving the test execution results per build ( via the xmlrpc interface).

The testreport does not scale in this scenario. Each new build is added to the left. Looks fine with a small set of builds however not so for a large number.

See attached screen shot

A solution is to request which set of builds to report on ( like the query report)
No tags attached.
png testreport.png (378,844) 2009-02-20 07:07
png TestReportMockup.png (103,876) 2009-02-21 02:30
Issue History
2009-02-20 07:07kcurranNew Issue
2009-02-20 07:07kcurranFile Added: testreport.png
2009-02-20 07:22kcurranNote Added: 0005559
2009-02-20 17:30fmanNote Added: 0005562
2009-02-21 02:30kcurranNote Added: 0005565
2009-02-21 02:30kcurranFile Added: TestReportMockup.png
2012-08-18 06:31fmanTask Workflow Status => TBD
2014-06-07 18:07fmanQA Team - Task Workflow StatusTBD => READY FOR TESTING
2014-06-07 18:07fmanStatusnew => resolved
2014-06-07 18:07fmanFixed in Version => 1.9.11 (2014 Q2 - bug fixing)
2014-06-07 18:07fmanResolutionopen => fixed
2014-06-07 18:07fmanAssigned To => fman
2014-07-28 20:33fmanStatusresolved => closed

2009-02-20 07:22   
ok, I can't tell my left from my right.

the description should say "Each new build is added to the right."
2009-02-20 17:30   
Please detail better your request (more detail, may be a mock up screen shoot)
2009-02-21 02:30   
I've attached a mock-up.

With the form, you would select which set of builds you have to report on.

To review the problem, the current testreport adds a column for every build. As the number of builds exceeds the screen size, the browser is forced to generate a sliding bar on the bottom so the user can slide the window to view the new column.
This situation will become unusable when the number of columns(builds) exceed a small set.

In our environment, there will be over 300 builds for a release which means this behaviour is unacceptable.