tests/: test reading from various profile setups

Add a testcase that tests the engine by reading from an exhaustive
combination of different profile types and states (missing databases,
empty databases, databases with values, databases with locks, etc).

Among other things, this makes sure the lockdown logic is sane.

This is the testcase that caught the bug fixed in the last commit
(listing with a missing database file).

1 files changed, 11 insertions, 5 deletions

diff --git a/tests/dconf-mock-gvdb.c b/tests/dconf-mock-gvdb.c
index cb639e3..6bc6d14 100644
--- a/tests/dconf-mock-gvdb.c
+++ b/tests/dconf-mock-gvdb.c
@@ -147,19 +147,25 @@ GVariant *
 gvdb_table_get_value (GvdbTable   *table,
                       const gchar *key)
 {
-  GHashTable *hash_table = (GHashTable *) table;
   DConfMockGvdbItem *item;
 
-  item = g_hash_table_lookup (hash_table, key);
+  item = g_hash_table_lookup (table->table, key);
 
-  return item ? g_variant_ref (item->value) : NULL;
+  return (item && item->value) ? g_variant_ref (item->value) : NULL;
 }
 
 gchar **
-gvdb_table_list (GvdbTable *table,
+gvdb_table_list (GvdbTable   *table,
                  const gchar *key)
 {
-  g_assert_not_reached ();
+  const gchar * const result[] = { "value", NULL };
+
+  g_assert_cmpstr (key, ==, "/");
+
+  if (!gvdb_table_has_value (table, "/value"))
+    return NULL;
+
+  return g_strdupv ((gchar **) result);
 }
 
 GvdbTable *