update readme and token scenario as per the review

Signed-off-by: Saad Khan <[email protected]>

tests/scripts/local_monitoring_tests/Local_monitoring_tests.md

@@ -184,11 +184,19 @@ Note: The test will fail if it's run as is if there are no matching workloads th
 
 ### Authentication Test:
 
-Kruize 0.1.1 supports the authentication which provides the user an option to pass authentication details in the yaml for the service they are using.
+Kruize 0.2 supports the authentication which provides the user an option to pass authentication details in the yaml for the service they are using.
 
 The authentication test is part of functional bucket and has a separate script similar to local_monitoring tests. It contains various valid and invalid scenarios for testing.
 
 It can be run as shown in the example below:
 
 `/test_autotune.sh -c <cluster-type> -i <image-name> -r benchmarks/ --testsuite=authentication_tests`
 
+#### Scenarios
+**_valid_**: a valid path to the token
+
+**_expired_**: an expired token value
+
+**_invalid_**: an invalid path to the token
+
+**_empty_**: a blank input in place of the token file path

tests/scripts/local_monitoring_tests/authentication_tests.sh

@@ -30,7 +30,7 @@ declare -A tokens
 tokens=(
   ["valid"]="/var/run/secrets/kubernetes.io/serviceaccount/token"
   ["expired"]="EXPIRED_TOKEN"
-  ["invalid"]="random-invalid-token-string"
+  ["invalid"]="/var/run/secrets/kubernetes.io/serviceaccount/token2"
   ["empty"]=""
 )
 # Tests to validate authentication types in Kruize