Displaying tests on a tab was designed for a user. It works best for devs if they've few tests failing so they can quickly see what's wrong and fix it. From that perspective anything >100 doesn't make sense, because it seems like global failure and you wouldn't fix it one-by-one anyway.

For code analysis I'd recommend relatively new feature - build warnings parser (https://confluence.atlassian.com/bamboo/configuring-build-warnings-parser-task-957148051.html). It's sent to Bitbucket Server and you can see it with your code.

For more automated tasks - processing xml tests results file would be much better in comparison to processing web page; whatever your use case is.

Showing more tests at once can quickly become a performance issue.

I like the idea about paging this data, but then it's more like improvement request. I'd love to see more interest before I can prioritise it on our roadmap.

We're using the tests to display code analysis results via test failures. Since we have a large code base, we have some cases where we have 2k or even more test failures. Since we can't view more than the first 1000 existing test failures and also not more than 1000 new test failures, this bug is a blocker for us. This doesn't allow me to quarantine or even get a proper overview for the test failures which sadly makes it unusable to work with large test suites.

Please allow to display all parsed test failures and paginate them or something similar, so that we can view the whole data the Junit parser has parsed.

Please consider setting the Symptom Severity to at least Major (A feature is unavailable, application performance is significantly degraded, or users job functions are impaired.), since Minor only matches when there is a workaround available and we're having some kind of (drastically spoken but somehow true) "data loss" in this case.