This mock expectation is problematic now, because "error in after all" is in both error messages and thus it doesn't demonstrate that the error is rescued and is printed out.  It would be good if they raised completely different error messages so that the examples aren't prone to this problem.