-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
-
None
-
NDS Sprint 18, NDS Sprint 19
The suite of "dashboard" e2e tests seems to fail intermittently:
C:\Users\Mike\workspace\ndslabs\gui>protractor --suite=dashboard
|
[13:05:25] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
|
[13:05:25] I/launcher - Running 1 instances of WebDriver
|
Started
|
.............
|
|
|
|
|
13 specs, 0 failures
|
Finished in 246.723 seconds
|
[13:09:35] I/launcher - 0 instance(s) of WebDriver still running
|
[13:09:35] I/launcher - chrome #01 passed
|
|
|
|
|
|
|
|
|
<then, running the same command without any changes to the code or test cases>
|
|
|
|
|
|
|
|
|
C:\Users\Mike\workspace\ndslabs\gui>protractor --suite=dashboard
|
[13:21:44] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
|
[13:21:44] I/launcher - Running 1 instances of WebDriver
|
Started
|
......A Jasmine spec timed out. Resetting the WebDriver Control Flow.
|
FA Jasmine spec timed out. Resetting the WebDriver Control Flow.
|
FA Jasmine spec timed out. Resetting the WebDriver Control Flow.
|
FA Jasmine spec timed out. Resetting the WebDriver Control Flow.
|
FA Jasmine spec timed out. Resetting the WebDriver Control Flow.
|
FA Jasmine spec timed out. Resetting the WebDriver Control Flow.
|
FA Jasmine spec timed out. Resetting the WebDriver Control Flow.
|
F
|
|
|
Failures:
|
1) Labs Workbench Dashboard View With Applications Running should link to available endpoints on the service
|
Message:
|
Expected 0 to be 1.
|
Stack:
|
<stack trace>
|
|
|
2) Labs Workbench Dashboard View With Applications Running should allow the user to change the label of an application
|
Message:
|
Expected 0 to be 1.
|
Stack:
|
<stack trace>
|
|
|
3) Labs Workbench Dashboard View With Applications Running should allow the user to view the console of a running application
|
Message:
|
Expected 0 to be 1.
|
Stack:
|
<stack trace>
|
|
|
4) Labs Workbench Dashboard View With Applications Running should allow the user to view the config of a running application
|
Message:
|
Expected 0 to be 1.
|
Stack:
|
<stack trace>
|
|
|
5) Labs Workbench Dashboard View With Applications Running should allow the user to view logs of a running application
|
Message:
|
Expected 0 to be 1.
|
Stack:
|
<stack trace>
|
|
|
6) Labs Workbench Dashboard View With Applications Running should link to the application's help documentation
|
Message:
|
Expected 0 to be 1.
|
Stack:
|
<stack trace>
|
|
|
7) Labs Workbench Dashboard View With Applications Running should allow the user to shutdown a running application
|
Message:
|
Expected 0 to be 1.
|
Stack:
|
<stack trace>
|
|
|
13 specs, 9 failures
|
Finished in 327.379 seconds
|
|
|
An error was thrown in an afterAll
|
AfterAll Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
|
|
|
An error was thrown in an afterAll
|
AfterAll Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
|
[13:27:14] I/launcher - 0 instance(s) of WebDriver still running
|
[13:27:14] I/launcher - chrome #01 failed 7 test(s)
|
[13:27:14] I/launcher - overall: 7 failed spec(s)
|
[13:27:14] E/launcher - Process exited with error code 1
|
This behavior seems to happen whether running locally or headless (the above log output was from running protractor locally).
More investigation is needed into the cause, but it seems to mainly affect the "With Applications Running" cases, and has to do with the tests expecting the user to have an application added and started. In all likelihood, there is a race condition in the beforeAll function of this block of the test code.
This ticket is complete when the Dashboard tests execute more reliably.
