changeset 95:6066d75a6d39

Rename expect_server_failure() to expect_client_failure(). Not that it's that much of a better name but at least no longer implies that we expect the server to fall over. What we expect is a server error code, and maybe eventually a client detection of that with friendly reporting to the user. Ha ha.
author mas01cr
date Wed, 03 Oct 2007 15:12:05 +0000
parents 03564e8988a2
children 8f7d0ae0ede4
files tests/0015/run-test.sh tests/test-utils.sh
diffstat 2 files changed, 3 insertions(+), 3 deletions(-) [+]
line wrap: on
line diff
--- a/tests/0015/run-test.sh	Wed Oct 03 14:13:05 2007 +0000
+++ b/tests/0015/run-test.sh	Wed Oct 03 15:12:05 2007 +0000
@@ -27,8 +27,8 @@
 
 check_server $!
 
-expect_server_failure ${AUDIODB} -c localhost:10015 -S -d /dev/null
-expect_server_failure ${AUDIODB} -c localhost:10015 -S -d /tmp/foo-does-not-exist
+expect_client_failure ${AUDIODB} -c localhost:10015 -S -d /dev/null
+expect_client_failure ${AUDIODB} -c localhost:10015 -S -d /tmp/foo-does-not-exist
 
 check_server $!
 
--- a/tests/test-utils.sh	Wed Oct 03 14:13:05 2007 +0000
+++ b/tests/test-utils.sh	Wed Oct 03 15:12:05 2007 +0000
@@ -67,7 +67,7 @@
   grep ${AUDIODB} /proc/$1/cmdline > /dev/null
 }
 
-expect_server_failure() {
+expect_client_failure() {
   # FIXME: work out whether and how the client should report server
   # errors.  At present, the client exits with a zero exit code.
   "$@"