-
Notifications
You must be signed in to change notification settings - Fork 244
Allow breaking the list of results in pages #39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This sounds like a nice enhancement. We could have a sensible default number of results and beyond that introduce pagination. My only concern is how filtering (#38) and sorting would be expected to work as these will be limited to the results on the page. It could simply be a not that's added to the page when pagination is present. |
I think that instead of just spitting the result in multiple "dumb" pages with a fixed number of tests in each (nobody said so, but it "felt" like the natural implementation of this enhancement), it would be nice to have the HTML pages structured in a hierarchy. In the common py.test use case, there will be Bonus point: the top-level html report summarizes everything, with a single line for each directory (file) stating how many run/pass/fail/etc and a link to the other HTML file with more details. |
I like this idea better than creating pagination. It's possible there will still be thousands of rows though if the tests are parameterised. Would splitting HTML files by module/class/function work for your needs @gmagno?
This is a great idea! |
That seems reasonable. |
Useful when you have thousands of tests and the browser struggles to open them all.
The text was updated successfully, but these errors were encountered: