For future reference, it would be better to just call MonitorBasedLRAdjuster.on_monitor directly. This would be more future-proof. The current version of the test could break if the behavior of the Train object changes. But Train is fairly stable, so I won't let this hold up the pull request.