+Get Karaf Log Types From Test Start
+ [Arguments] ${ip} ${test_name} ${types} ${user}=${ODL_SYSTEM_USER} ${password}=${ODL_SYSTEM_PASSWORD} ${prompt}=${ODL_SYSTEM_PROMPT}
+ ... ${log_file}=${KARAF_LOG}
+ [Documentation] A wrapper keyword for "Get Karaf Log Type From Test Start" so that we can parse for multiple types
+ ... of log messages. For example, we can grab all messages of type WARN and ERROR
+ FOR ${type} IN @{types}
+ Get Karaf Log Type From Test Start ${ip} ${test_name} ${type} ${user} ${password}
+ ... ${prompt} ${log_file}
+ END
+
+Get Karaf Log Events From Test Start
+ [Arguments] ${test_name} ${user}=${ODL_SYSTEM_USER} ${password}=${ODL_SYSTEM_PASSWORD} ${prompt}=${ODL_SYSTEM_PROMPT}
+ [Documentation] Wrapper for the wrapper "Get Karaf Log Types From Test Start" so that we can easily loop over
+ ... any number of controllers to analyze karaf.log for ERROR, WARN and Exception log messages
+ ${log_types} = Create List ERROR WARN Exception
+ FOR ${i} IN RANGE 1 ${NUM_ODL_SYSTEM} + 1
+ Get Karaf Log Types From Test Start ${ODL_SYSTEM_${i}_IP} ${test_name} ${log_types}
+ END
+
+Fail If Exceptions Found During Test Deprecated
+ [Arguments] ${test_name} ${exceptions_white_list}=${EMPTY}
+ [Documentation] Create a failure if an Exception is found in the karaf.log. Will work for single controller jobs
+ ... as well as 3node cluster jobs
+ FOR ${i} IN RANGE 1 ${NUM_ODL_SYSTEM} + 1
+ Verify Exception Logging In Controller ${ODL_SYSTEM_${i}_IP} ${test_name} ${exceptions_white_list}
+ END
+
+Verify Exception Logging In Controller
+ [Arguments] ${controller_ip} ${test_name} ${exceptions_white_list}
+ [Documentation] Local keyword to make it easier to loop through N controllers to pull Exceptions from the
+ ... karaf.log file and validate with "Check Against White List"
+ ${exceptions}= Get Karaf Log Type From Test Start ${controller_ip} ${test_name} Exception
+ @{log_lines}= Split String ${exceptions} ${\n}
+ ${num_log_entries} Get Length ${log_lines}
+ Return From Keyword If ${num_log_entries} == ${0} No Exceptions found.
+ FOR ${log_message} IN @{log_lines}
+ Check Against White List ${log_message} ${exceptions_white_list}
+ END
+
+Check Against White List
+ [Arguments] ${exception_line} ${exceptions_white_list}
+ [Documentation] As soon as the ${exceptions_line} is found in one of the elements of ${exceptions_white_list}
+ ... this keyword will exit and give a Pass to the caller. If there is no match, this keyword will end up
+ ... marking a failure. In the case that no exceptions are found, the caller could end up passing a single
+ ... empty line as that is what is returned when a grep on karaf.log has no match, so we can safely return
+ ... in that case as well.
+ Return From Keyword If "${exception_line}" == ""
+ FOR ${exception} IN @{exceptions_white_list}
+ Return From Keyword If "${exception}" in "${exception_line}" Exceptions found, but whitelisted: ${\n}${exception_line}${\n}
+ END
+ Fail Exceptions Found: ${\n}${exception_line}${\n}
+
+Wait_For_Karaf_Log
Code Review / integration / test.git / blobdiff