svn rev #21868: trunk/src/kadmin/ passwd/unit-test/kpasswd.0/ testing/scripts/

[raeburn@MIT.EDU]

http://src.mit.edu/fisheye/changelog/krb5/?cs=21868
Commit By: raeburn
Log Message:
ticket: 6358

Revise last change to better resemble the original test, keeping the
min-lifetime test code collected together.  Change policy to have a
minimum password lifetime of 10s instead of 30s, and reduce the test
delays accordingly.


Changed Files:
U   trunk/src/kadmin/passwd/unit-test/kpasswd.0/changing.exp
U   trunk/src/kadmin/testing/scripts/init_db
Modified: trunk/src/kadmin/passwd/unit-test/kpasswd.0/changing.exp
===================================================================
--- trunk/src/kadmin/passwd/unit-test/kpasswd.0/changing.exp	2009-02-02 19:29:52 UTC (rev 21867)
+++ trunk/src/kadmin/passwd/unit-test/kpasswd.0/changing.exp	2009-02-02 20:37:41 UTC (rev 21868)
@@ -12,23 +12,8 @@
 # Here are the tests
 #
 
-# Under "make check", init_db will just have been run and we could
-# jump right into the too-soon test.  But if someone is working with
-# the test suite manually, init_db may have been run a while ago.
-# So, force some known state, first.
-verbose "(sleeping 30 seconds so pol2 password can be changed)"
-sleep 30
+set pol2_time [timestamp]
 
-test_win {pol2} {successful change} pol2 pol222222 polbbbbbb
-
-set pol2_time [expr 31 + [timestamp]]
-
-test_3pass {pol2} {D.15: too soon to change password} pol2 \
-	polbbbbbb pol333333 pol333333 \
-	4 {Password cannot be changed because it was changed too recently.  Please wait until .*[12][0-9][0-9][0-9] before you change it.  If you need to change your password before then, contact your system security administrator.}
-
-#
-
 test_3pass {test2} {D.5: different new passwords} test2 test2 test2 foobar \
 	4 {New passwords do not match - password not changed.}
 
@@ -106,11 +91,23 @@
 test_win {pol1} {successful change} pol1 polBBBBBB polCCCCCC
 test_win {pol1} {successful change} pol1 polCCCCCC pol111111
 
-# Now delay a little longer (if needed) and try changing pol2's
-# password again.
-set delay [expr $pol2_time - [timestamp]]
-verbose "(sleeping $delay seconds)"
+# Under "make check", init_db will just have been run and we could
+# jump right into the too-soon test.  But if someone is working with
+# the test suite manually, init_db may have been run a while ago.
+# So, force some known state, first.
+set delay [expr $pol2_time + 11 - [timestamp]]
+verbose "(sleeping $delay seconds so pol2 password can be changed)"
 sleep $delay
 
-test_win {pol2} {password min life passed} pol2 polbbbbbb pol333333
+test_win {pol2} {successful change} pol2 pol222222 polbbbbbb
 
+test_3pass {pol2} {D.15: too soon to change password} pol2 \
+	polbbbbbb pol222222 pol222222 \
+	4 {Password cannot be changed because it was changed too recently.  Please wait until .*[12][0-9][0-9][0-9] before you change it.  If you need to change your password before then, contact your system security administrator.}
+
+# Now delay a little longer (if needed) and try changing pol2's
+# password again.
+verbose "(sleeping 10 seconds)"
+sleep 10
+
+test_win {pol2} {password min life passed} pol2 polbbbbbb pol222222

Modified: trunk/src/kadmin/testing/scripts/init_db
===================================================================
--- trunk/src/kadmin/testing/scripts/init_db	2009-02-02 19:29:52 UTC (rev 21867)
+++ trunk/src/kadmin/testing/scripts/init_db	2009-02-02 20:37:41 UTC (rev 21868)
@@ -106,7 +106,7 @@
 
     {ovsec_kadm_create_policy $server_handle "test-pol 0 10000 8 2 3 0" \
 	    {OVSEC_KADM_POLICY OVSEC_KADM_PW_MIN_LENGTH OVSEC_KADM_PW_MIN_CLASSES OVSEC_KADM_PW_MAX_LIFE OVSEC_KADM_PW_HISTORY_NUM}}
-    {ovsec_kadm_create_policy $server_handle "once-a-min 30 0 0 0 0 0" \
+    {ovsec_kadm_create_policy $server_handle "once-a-min 10 0 0 0 0 0" \
 	    {OVSEC_KADM_POLICY OVSEC_KADM_PW_MIN_LIFE}}
     {ovsec_kadm_create_policy $server_handle "dict-only 0 0 0 0 0 0" \
 	    {OVSEC_KADM_POLICY}}