test: firmware notYetStarted: canHandleBlob
For thoroughness just add a test that should pass if the getBlobIds
returns correctly. In theory, one could break the linkage between those
two commands and introduce a regression.
Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: I4228b69c32666348353cc8af56203ddbdc2cc9b1
diff --git a/test/firmware_state_notyetstarted_unittest.cpp b/test/firmware_state_notyetstarted_unittest.cpp
index 85a664a..0cc724d 100644
--- a/test/firmware_state_notyetstarted_unittest.cpp
+++ b/test/firmware_state_notyetstarted_unittest.cpp
@@ -55,6 +55,11 @@
EXPECT_THAT(handler->getBlobIds(),
UnorderedElementsAreArray(expectedBlobs));
+
+ for (const auto& blob : expectedBlobs)
+ {
+ EXPECT_TRUE(handler->canHandleBlob(blob));
+ }
}
/* TODO: Try deleting some blobs -- in this state it should just return failure,