When data is written with WriteU64, it should be tested with ReadU64,
authorAlexander Krotov <ilabdsf@yandex.ru>
Sun, 02 Aug 2015 20:44:01 +0300
changeset 11556 bdebcc180265
parent 11555 7e7d59586f2d
child 11557 2406eb3c37b0
child 11558 68e480bb7d74
When data is written with WriteU64, it should be tested with ReadU64, not ReadLsbtohU64.
src/network/test/buffer-test.cc
--- a/src/network/test/buffer-test.cc	Sun Aug 02 19:26:37 2015 +0300
+++ b/src/network/test/buffer-test.cc	Sun Aug 02 20:44:01 2015 +0300
@@ -156,9 +156,8 @@
   buff64.AddAtStart (8);
   i = buff64.Begin ();
   i.WriteU64 (0x0123456789ABCDEFllu);
-  ENSURE_WRITTEN_BYTES (buff64, 8, 0xef, 0xcd, 0xab, 0x89, 0x67, 0x45, 0x23, 0x01);
   i = buff64.Begin ();
-  NS_TEST_ASSERT_MSG_EQ (i.ReadLsbtohU64 (), 0x0123456789abcdefllu, "Could not read expected value");
+  NS_TEST_ASSERT_MSG_EQ (i.ReadU64 (), 0x0123456789abcdefllu, "Could not read expected value");
   i = buff64.Begin ();
   i.WriteHtolsbU64 (0x0123456789ABCDEFllu);
   ENSURE_WRITTEN_BYTES (buff64, 8, 0xef, 0xcd, 0xab, 0x89, 0x67, 0x45, 0x23, 0x01);