|
Possible Error Conditions |
Expected behavior and Solution |
|---|---|
|
Expected at the time of launching the debugger |
|
|
The config file path is invalid |
In case of occurrence of any of these errors the debugger does not get launched. You can try and launch the debugger again after the error has been fixed. |
|
Property file contains invalid properties |
|
|
Invalid logpath set in config path |
|
|
No test case iterations to execute. Need at least one iteration to execute test case. |
|
|
A generic exception has occurred in initializing the test execution engine |
|
|
No tests to execute |
|
|
Expected during test case execution |
|
|
Unable to launch browser due to one of the following possible reasons:
|
Expected during test case execution, the execution report will not be generated in case of any of these exceptions. |
|
An error occurred in calculating roll up status |
|
|
Report file not found |
|
|
An error occurred in updating the summary report |
|
|
An error occurred in releasing the report |
|
|
Unable to write to the report file |
|
|
Expected during test case execution |
|
|
Invalid Expression Exception occurred |
The test case execution report will be generated even if these exceptions occur. |
|
Selenium clean up failed, error occurred in cleaning up the Selenium Webdriver. |
|
|
Expected at the time of launching the debugger or at the time of test execution. |
|
|
A generic exception has occurred along with the exact cause of the error |
Debugger either does not get launched or stops the execution depending on the wherever the error occurs. Debugger also shows the Error message from the test execution engine in this case. |