#
#
# add_dir "tests/wrong_options_override_workspace_options"
# 
# add_file "tests/wrong_options_override_workspace_options/__driver__.lua"
#  content [949a6e38cd83c5f621bfb9e474fb07fff28ab04e]
#
============================================================
--- tests/wrong_options_override_workspace_options/__driver__.lua	949a6e38cd83c5f621bfb9e474fb07fff28ab04e
+++ tests/wrong_options_override_workspace_options/__driver__.lua	949a6e38cd83c5f621bfb9e474fb07fff28ab04e
@@ -0,0 +1,35 @@
+--
+-- Up until 0.40 mtn overwrote the database and keydir entries
+-- in _MTN/options with the options specified by the user
+-- without checking them further. This lead to workspace corruption
+-- and the user had to edit _MTN/options by hand to let it point
+-- to the valid entries again. This test ensures that at least
+-- some basic file path / type checking is done on both, the
+-- --database and --keydir options before they're actually written
+-- to _MTN/options
+--
+
+-- setup a very simple workspace
+mtn_setup()
+check(mtn_ws_opts("add", "."), 0, false, false)
+
+-- try to check the status and supply a non-existing database argument
+-- FIXME: this silently succeeds in a newly created workspace and should
+-- fail as soon as there is at least one ancestor, but this is another
+-- cup of tea
+check(mtn_ws_opts("status", "-d", "baz"), 0, false, false)
+
+-- this should succeed if the original database is still set
+check(mtn_ws_opts("commit", "-m", "test"), 0, false, false)
+
+--
+-- now the keydir check, we do a minor change - to see the error,
+-- comment out the previous commit
+--
+check(mtn_ws_opts("attr", "set", ".", "foo", "bar"), 0, false, false)
+
+writefile("not_a_dir", "bla")
+check(mtn_ws_opts("status", "--keydir", "not_a_dir"), 0, false, false)
+
+check(mtn_ws_opts("commit", "-m", "another test"), 0, false, false)
+