|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
4 hours
|
|
|
Remaining Estimate:
|
4 hours
|
|
|
Time Spent:
|
Not Specified
|
|
|
|
|
Some open source projects like Jetty, Wicket or OpenJPA have a large number of unit tests. Think about hundreds or even thousands. Selecting the 'tests' report is in those cases extremely slow since it takes a lot of time to build up a huge page. It would be nice if in those cases the unit tests were paginated, summarized, or dynamically loaded through AJAX. This is in the viewBuildResultsTests.action screen.
|
|
Description
|
Some open source projects like Jetty, Wicket or OpenJPA have a large number of unit tests. Think about hundreds or even thousands. Selecting the 'tests' report is in those cases extremely slow since it takes a lot of time to build up a huge page. It would be nice if in those cases the unit tests were paginated, summarized, or dynamically loaded through AJAX. This is in the viewBuildResultsTests.action screen. |
Show » |
|
Improvement
Resolved
Major
Better handling of large number of unit tests
Yeah there ae definitely places where we can really benefit from pagination, and we'll be trying to add that in for the next point release. The test page is one of them and the results page is the other obvious candidate.
Thanks for the comments!
Cheers,
Mark C