4.2 servers may optimize away aggregation pipelines that can be computed using a query (SERVER-24860). This caused an unexpected test failure in testExplainOption, since the test was looking for a "stages" field within the aggregate result's first and only document. We do not map the explain result (unlike RUBY-1788), so a quick fix would just be to relax this assertion to allow either "stages" or "queryPlanner".