This test framework class mocks a bit too heavily, and simulates CS internal behaviour with the mock methods over a point it is reasonably maintainable, any internal change in CS is a major headscratch.
A lot of tests depend on this class, so we should approach it carefully, but I think it's wroth to examine this class if it can be made a bit more resilient to changes, and easier to maintain. Or at least document it better.
- is depended upon by
YARN-10273 [Umbrella] Followup tasks for CapacityScheduler leaf queue changes (YARN-9879)