Problem/Motivation
#3508631: Load project data from a new QueryManager class that implements a centralized, static cache added the critical front-end infrastructure needed to display multiple project browsers on a single page.
In #3509184: Add a test of multiple project browsers on a page tests were written to validate this feature. Testing pagination for multiple instances on single page still needs to be done.
Steps to reproduce
Proposed resolution
Issue fork project_browser-3509674
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
phenaproximaPostponed on #3509406: Add more projects to ProjectBrowserTestMock's fixture.
Comment #3
narendrarI think we can click 'Clear filters' as done in
ProjectBrowserUiTest::testPaging()to test this.Comment #4
narendrarThis is blocked on #3509184: Add a test of multiple project browsers on a page
Comment #5
phenaproximaComment #6
narendrarComment #8
narendrarComment #9
phenaproximaI ❤️ this. It's essential coverage that we'll need in the wake of #3510506: Allow the project browser render element to take a customized pagination and predefined sort, and force max_selections to be global, which shows that pagination is the main thing that allows project browsers to be minified in the first place.
I made some relatively minor changes and factored out some helper methods, but the structure of the test remains in place. It's great work. Since we've got a shortage of reviewers at the moment, I'm calling this one RTBC and will go over it with Tim.
Comment #12
tim.plunkettThis is so clean, love to see it.
Merged !773 🎉