[ZEPPELIN-942] CASE III of ZeppelinIT failure - Configuration page visited, instead of Interpreter

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.6.0
• Assignee: Prabhjyot Singh
• Reporter: Alexander Bezzubov
• Created: 02/Jun/16 08:44
• Updated: 05/Jun/16 12:43
• Resolved: 04/Jun/16 08:25

Description

2 similar failures, when on `ZeppelinIT.testSparkInterpreterDependencyLoading` Interpreter page was not visited (it was Configuration or Main page instead)

#946 - https://s3.amazonaws.com/archive.travis-ci.org/jobs/134570147/log.txt
#860 - https://s3.amazonaws.com/archive.travis-ci.org/jobs/134671260/log.txt

Running org.apache.zeppelin.integration.SparkParagraphIT

	at org.apache.zeppelin.integration.SparkParagraphIT.startUp(SparkParagraphIT.java:47)
Caused by: org.openqa.selenium.NoSuchElementException: Unable to locate element: {"method":"partial link text","selector":"Create new note"}

...
Running org.apache.zeppelin.integration.ZeppelinIT

	at org.apache.zeppelin.integration.ZeppelinIT.testSparkInterpreterDependencyLoading(ZeppelinIT.java:243)
Caused by: org.openqa.selenium.NoSuchElementException: Unable to locate element: {"method":"xpath","selector":"//div[@id='spark']//form//button[1]"}

From the screenshot - it looks like test ends up on Configuration page, instead of Interpreter page

Issue Links

• is duplicated by: ZEPPELIN-950 Fix flaky ZeppelinIT build