[3/5] msi/tests: Use a unique product code when testing MsiConfigureFeature parameter validation.

Hans Leidekker hans at codeweavers.com
Tue Apr 27 06:29:49 CDT 2010


This is to avoid ERROR_INSTALL_ALREADY_RUNNING errors on Windows.
---
 dlls/msi/tests/msi.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/dlls/msi/tests/msi.c b/dlls/msi/tests/msi.c
index 4bc59ac..a05abeb 100644
--- a/dlls/msi/tests/msi.c
+++ b/dlls/msi/tests/msi.c
@@ -247,10 +247,10 @@ static void test_null(void)
     r = MsiConfigureFeatureA("{00000000-0000-0000-0000-000000000000}", NULL, 0);
     ok( r == ERROR_INVALID_PARAMETER, "wrong error\n");
 
-    r = MsiConfigureFeatureA("{00000000-0000-0000-0000-000000000000}", "foo", 0);
+    r = MsiConfigureFeatureA("{00000000-0000-0000-0000-000000000001}", "foo", 0);
     ok( r == ERROR_INVALID_PARAMETER, "wrong error %d\n", r);
 
-    r = MsiConfigureFeatureA("{00000000-0000-0000-0000-000000000000}", "foo", INSTALLSTATE_DEFAULT);
+    r = MsiConfigureFeatureA("{00000000-0000-0000-0000-000000000002}", "foo", INSTALLSTATE_DEFAULT);
     ok( r == ERROR_UNKNOWN_PRODUCT, "wrong error %d\n", r);
 
     /* make sure empty string to MsiGetProductInfo is not a handle to default registry value, saving and restoring the
-- 
1.7.0.4







More information about the wine-patches mailing list