firmware: start implementing deleteBlob
If a client sends a deleteBlob, two things should happen. The active
blob is cleared and the states are all reset, effectively like an abort.
Change-Id: I54f2986b7cad9b7fc117d36a8e631e84c8e8feb8
Signed-off-by: Patrick Venture <venture@google.com>
diff --git a/test/Makefile.am b/test/Makefile.am
index e914c14..4144e4b 100644
--- a/test/Makefile.am
+++ b/test/Makefile.am
@@ -16,7 +16,8 @@
firmware_open_unittest \
firmware_write_unittest \
firmware_writemeta_unittest \
- firmware_close_unittest
+ firmware_close_unittest \
+ firmware_delete_unittest
TESTS = $(check_PROGRAMS)
@@ -40,3 +41,6 @@
firmware_close_unittest_SOURCES = firmware_close_unittest.cpp
firmware_close_unittest_LDADD = $(top_builddir)/firmware_handler.o
+
+firmware_delete_unittest_SOURCES = firmware_delete_unittest.cpp
+firmware_delete_unittest_LDADD = $(top_builddir)/firmware_handler.o