Edit non-unique TEST_NAME variable

testenv/ChangeLog

@@ -1,3 +1,8 @@
+2013-08-31  Darshit Shah  <darnir@gmail.com>
+
+	* README: Explain that TEST_NAME needs to be unique
+	* Test-auth-no-challenge.py: Edit non-unique TEST_NAME
+
 2013-08-31  Darshit Shah  <darnir@gmail.com>
 
 	* HTTPTest.py (ServerError): Define new Exception for handling

testenv/README

@@ -206,6 +206,13 @@ also be added to the XFAIL_TESTS variable. This will allow expected failures to
 pass through. If a test mentioned in the XFAIL_TESTS variable passes, it gets
 red-flagged as a XPASS.
 
+Remember to always name the Test correctly using the TEST_NAME variable. This
+is essential since a directory with the Test Name is created and this can
+cause synchronization problems when the Parallel Test Harness is used.
+One can use the following command on Unix systems to check for TEST_NAME
+clashes:
+$ grep -r -h "TEST_NAME =" | cut -c13- | uniq -c -d
+
 Requirements:
 ================================================================================
 

testenv/Test-auth-no-challenge.py

@@ -6,7 +6,7 @@ from WgetTest import HTTPTest, WgetFile
     This test ensures Wget's Basic Authorization Negotiation, when the
     --auth-no-challenge command is used.
 """
-TEST_NAME = "Digest Authorization"
+TEST_NAME = "Auth No Challenge Command"
 ############# File Definitions ###############################################
 File1 = "Need a cookie?"