The leaking PageNumberNotFoundException that caused T289728 is now handled in three places:
- addPageNsNavigation
- PageContentBuilder
- PageContent
Of these, only PageContentBuilder has a test that can verify anys exception relating to an invalid page number are caught correctly.
The other two code paths are also fixed in T289728, but they should also have tests that can check invalid page numbers won't throw exceptions.