tests: Fix Maintenance1Tests to handle lack of extension
Wait to create the device until the extension is known to be there
Change-Id: I3be8218cca439b7843133c1666cdb7119634cf49
diff --git a/tests/layer_validation_tests.cpp b/tests/layer_validation_tests.cpp
index 436736e..9a6f777 100644
--- a/tests/layer_validation_tests.cpp
+++ b/tests/layer_validation_tests.cpp
@@ -22553,7 +22553,7 @@
TEST_DESCRIPTION("Validate various special cases for the Maintenance1_KHR extension");
device_extension_names.push_back(VK_KHR_MAINTENANCE1_EXTENSION_NAME);
- ASSERT_NO_FATAL_FAILURE(Init());
+ InitFramework(instance_layer_names, instance_extension_names, device_extension_names, myDbgFunc, m_errorMonitor);
// Ensure that extension is available and enabled.
uint32_t extension_count = 0;
@@ -22579,7 +22579,7 @@
}
m_errorMonitor->ExpectSuccess();
-
+ ASSERT_NO_FATAL_FAILURE(InitState());
VkCommandBuffer cmd_buf;
VkCommandBufferAllocateInfo alloc_info;
alloc_info.sType = VK_STRUCTURE_TYPE_COMMAND_BUFFER_ALLOCATE_INFO;