The number of items per page has caused confusion

[David_Rumble]

Hi,

We have added a number of new viewers to Testiny and a common point of confusion is the “per page” option limiting the number of items in view.
I understand that you are probably limiting the amount of data a single request makes to the server, but I have had multiple people complain that the total tests in view does not equal the total. This is because they are within folders.
By default they will have the setting Auto and they would need to know that they need to set 500 in order to see the items, or scroll using the (easy to miss) page buttons. This is not very intuitive and can cause confusion.

E.g. set to “Auto”:

Changing the setting to “500”:

There’s not even that many tests in this example test run, but it’s still needed to increase the “per page” setting to see the folders.
Setting to a new global default of 500 would temporarily solve the issue, but the problem would come back after the number of tests go past this.

Maybe it would be better if the test folders were always visible but collapsed (regardless of the “per page” setting), with the tests populated on expansion?

Or perhaps make it obvious that there are more folders / tests to reveal (like a “x tests hidden” note at the bottom, or something)?

[Alex_Hoisl]

Thank you very much for the detailed feedback!

I can see in the screenshots that the usability is not very good and can lead to confusion.
In the current implementation, it does not really matter if you have folders collapsed or not - the table will always just get the number of test cases selected in the page size, even if they are hidden in a collapsed folder.

Unfortunately, this is not easily changed, however we will try to improve the usability and trying to make it clearer that only part of the test cases got loaded.
Eventually, maybe an infinite scroll list (that loads further test cases when space is available) would be more useful when collapsing folders - we will evaluate this.

If somebody reads this request and also had similar experience, make sure to vote for this topic. We do consider the number of votes for feature requests in our roadmap and priority planning.

Best regards,
Alex