Thanks for your posting and for the UI feedback.
- The pagination/limit feature on the run/suite pages was added because it can take some time to render really large test suites, even with modern browsern (with older browser versions even more) and depending on the view mode (full/compact). So to ensure a good performance for all pages in TestRail, we added the limit feature. Often times when you navigate to a test suite you don’t need the full list of cases and this feature is meant as a compromise between good page load times and usability.
We usually recommend opening test/test cases from the overview pages in separate browser tabs and then closing the tab when you are finished with the test/test case. This way you won’t loose your position and state on the overview page and don’t need to navigate back and forth between the run and the tests (or suites and test cases).
Some test/test cases aspects are also directly available on the overview pages so that you don’t need to open the individual test/test case pages at all (e.g. changing the case title, adding results or assigning tests). There are also the previous/next buttons in the test/test case toolbars (at the top of the test/test case pages) to quickly navigate to the previous/next test/test case, just in case you haven’t seen them.
This is something we would like to improve in a future version of TestRail by adding a context menu to the table (rows) with test related actions (adding results, assigning tests, etc.), so that you don’t have to scroll down every time you want to add a result for multiple tests. Please note that you can already add a single result by pressing the status box on the right of a test row.
This is a feature request we’ve got before and we will definitely look into making this easier. We do already have a few ideas for this and I’m sure this will be improved in a future version of TestRail.
Thanks again and please let me know in case you have any additional feedback or questions.