diff options
author | Jameson Graef Rollins <jrollins@finestructure.net> | 2009-02-17 19:16:58 -0500 |
---|---|---|
committer | Jameson Graef Rollins <jrollins@finestructure.net> | 2009-02-17 19:16:58 -0500 |
commit | 72f145629c3c626a30aa08e6100f298cd31a30c2 (patch) | |
tree | 48e25fe364c1cdb26e8d3cc3f4714b5f13d79b03 | |
parent | d2874b94fedbe6d043d44ca3562879251e6ea10f (diff) |
add README to tests/ directory
-rw-r--r-- | tests/README | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/tests/README b/tests/README new file mode 100644 index 0000000..2bc981c --- /dev/null +++ b/tests/README @@ -0,0 +1,31 @@ +Monkeysphere test infrastructure +================================ + +These are scripts to test various aspects of the Monkeysphere system. + +Some notes about getting started working on the monkeysphere test +infrastructure: + +- the tests can and should be run as a non-privileged user. since the + tests do potentially destructive things (like wiping out and + recreating gpg keyrings) they should definitely *not* be run as + root. it may even be advisable to run them as a different, + dedicated user, so that any goofs you make while updating the test + infrastructure don't compromise your main account. + +- you do not need the monkeysphere package installed locally, though + you will need the monkeysphere dependencies installed locally. + +- the idea with this script is to do the following: + + - set up test server infrastructure + - test the server setup + - set up test user + - test an ssh connection between test user and test server + - modify server/user setup and rerun ssh_test to make sure it + suceeds/fails as expected + +- there are various FIXMEs in the script that outline some of the + further testing that should be undertaken. + +- good documentation in the code in the form of comments are needed. |