It's no longer necessary to explicitly mark newline() as unexpected, since we're using a strict mock now.

Not only is it unnecessary, it was generating confusing error messages if
newline() was expected but occurred out of order.

1 files changed, 0 insertions, 5 deletions

diff --git a/tests/test_transient_message.cc b/tests/test_transient_message.cc
index 98ddbc1a..1b58515c 100644
--- a/tests/test_transient_message.cc
+++ b/tests/test_transient_message.cc
@@ -89,11 +89,6 @@ namespace
     {
       EXPECT_CALL(*term_locale, wcwidth(two_column_char))
         .WillRepeatedly(Return(2));
-
-      // The tests should never scroll past the first line (that's the
-      // whole point of the transient message object, after all).
-      EXPECT_CALL(*teletype, newline())
-        .Times(0);
     }
   };
 }