security-manager-tests: use real privilege names

Security-manager recently implemented user profiles, allowing only
selected privileges for each user type. For now, all user profiles
can utilize all specified Tizen 3.0 privileges. But security-tests
used to test security-manager with custom privilege names that are
now not permitted. To put tests back to work privilege names must
be valid.

Change-Id: I78d972b67ac192f16d218f666e3614d8da136c74
Signed-off-by: Rafal Krypa <r.krypa@samsung.com>

diff --git a/tests/security-manager-tests/security_manager_tests.cpp b/tests/security-manager-tests/security_manager_tests.cpp
index 903ce94..0f58d93 100644 (file)
--- a/tests/security-manager-tests/security_manager_tests.cpp
+++ b/tests/security-manager-tests/security_manager_tests.cpp
@@ -31,13 +31,13 @@ using namespace SecurityManagerTest;
 DEFINE_SMARTPTR(cap_free, _cap_struct, CapsSetsUniquePtr);
 
 static const privileges_t SM_ALLOWED_PRIVILEGES = {
-    "security_manager_test_rules2_r",
-    "security_manager_test_rules2_no_r"
+    "http://tizen.org/privilege/location",
+    "http://tizen.org/privilege/camera"
 };
 
 static const privileges_t SM_DENIED_PRIVILEGES  = {
-    "security_manager_test_rules1",
-    "security_manager_test_rules2"
+    "http://tizen.org/privilege/bluetooth",
+    "http://tizen.org/privilege/power"
 };
 
 static const privileges_t SM_NO_PRIVILEGES  = {