[1/2] wintrust/tests: Fix checks to be more informative when they fail.

Francois Gouget fgouget at codeweavers.com
Tue Jun 12 10:58:44 CDT 2007


---

It's just irritating when the test fails but does not say what it 
expected and what it got instead.

 dlls/wintrust/tests/register.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/dlls/wintrust/tests/register.c b/dlls/wintrust/tests/register.c
index db5726c..334a99a 100644
--- a/dlls/wintrust/tests/register.c
+++ b/dlls/wintrust/tests/register.c
@@ -325,14 +325,14 @@ static void test_RegPolicyFlags(void)
     ok(!r, "RegQueryValueEx failed: %d\n", r);
 
     pGetFlags(&flags2);
-    ok(flags1 == flags2, "Didn't get expected flags\n");
+    ok(flags1 == flags2, "Got %08x flags instead of %08x\n", flags1, flags2);
 
     flags3 = flags2 | 1;
     ret = pSetFlags(flags3);
     ok(ret, "pSetFlags failed: %d\n", GetLastError());
     size = sizeof(flags1);
     r = RegQueryValueExA(key, State, NULL, NULL, (LPBYTE)&flags1, &size);
-    ok(flags1 == flags3, "Didn't get expected flags\n");
+    ok(flags1 == flags3, "Got %08x flags instead of %08x\n", flags1, flags3);
 
     pSetFlags(flags2);
 
-- 
1.4.4.4




More information about the wine-patches mailing list