From 43ee2ee192bd826fe02a8155096e4e3f12670977 Mon Sep 17 00:00:00 2001
From: Anton Kolesnyk <41349689+antkmsft@users.noreply.github.com>
Date: Fri, 7 May 2021 16:11:41 +0000
Subject: [PATCH] Additional tests for Nullable<T> (#2215)

Closes #1786
---
 sdk/core/azure-core/test/ut/nullable.cpp | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/sdk/core/azure-core/test/ut/nullable.cpp b/sdk/core/azure-core/test/ut/nullable.cpp
index 8dc8535e3..1ca22d7f7 100644
--- a/sdk/core/azure-core/test/ut/nullable.cpp
+++ b/sdk/core/azure-core/test/ut/nullable.cpp
@@ -207,3 +207,20 @@ TEST(Nullable, PreCondition3)
   ASSERT_DEATH(Foo(Nullable<int>().Value());, "Empty Nullable");
 #endif
 }
+
+TEST(Nullable, Operator)
+{
+  Nullable<std::string> val1("12345");
+  EXPECT_EQ(*val1, "12345");
+  val1->append("aaaa");
+  EXPECT_EQ(*val1, "12345aaaa");
+}
+
+TEST(Nullable, Move)
+{
+  Nullable<std::unique_ptr<int>> val(std::make_unique<int>(123));
+  std::unique_ptr<int> const taken = *std::move(val);
+  EXPECT_TRUE(taken);
+  EXPECT_EQ(*taken, 123);
+  // val.HasValue() would return true, but accessing a value after it has been moved is UB anyways.
+}