Skip to content
This repository has been archived by the owner. It is now read-only.

Selenium test case fails to exceute properly #413

Closed
lukeis opened this issue Mar 2, 2016 · 5 comments
Closed

Selenium test case fails to exceute properly #413

lukeis opened this issue Mar 2, 2016 · 5 comments

Comments

@lukeis
Copy link
Member

@lukeis lukeis commented Mar 2, 2016

Originally reported on Google Code with ID 413

What steps will reproduce the problem?
1. Install Selenium 1.0.5
2. add "patch" of Selenium per Issue 401
3.Run test case per "http://seleniumhq.org/movies/intro.mov"

What is the expected output? 
Expected to go the wiki page and no errors in the log pane at the bottom
What do you see instead?
Does not go to the wiki page and error in the log pane

What version of the product are you using? On what operating system?
Selenium 1.0.5 in Vista home premium with firefox 3.5.8

Please provide any additional information below.

Reported by rahim.sayeef on 2010-03-09 00:49:47


- _Attachment: [seleniumTC2.html](https://storage.googleapis.com/google-code-attachments/selenium/issue-413/comment-0/seleniumTC2.html)_ - _Attachment: seleniumError.png
![seleniumError.png](https://storage.googleapis.com/google-code-attachments/selenium/issue-413/comment-0/seleniumError.png)_ - _Attachment: [seleniumTC2.html](https://storage.googleapis.com/google-code-attachments/selenium/issue-413/comment-0/seleniumTC2.html)_ - _Attachment: [SeleniumTC1.gif](https://storage.googleapis.com/google-code-attachments/selenium/issue-413/comment-0/SeleniumTC1.gif)_
@lukeis

This comment has been minimized.

Copy link
Member Author

@lukeis lukeis commented Mar 2, 2016

Reported by jari.bakken on 2011-01-27 02:23:19

  • Labels added: Component-IDE
@lukeis

This comment has been minimized.

Copy link
Member Author

@lukeis lukeis commented Mar 2, 2016

Google isn't really a good sample anymore with the the roll out of instant search (or
whatever it is called). It looks like this is exactly what you are hitting. We should
change that...

Anyways, if you put a waitForElementPresent  before the click of the link= line it
gets beyond that point. I've added my 'working' script to the bug.

Reported by adamgoucher on 2011-02-01 03:30:19

  • Status changed: Invalid

- _Attachment: [seleniumTC2-1.html.xhtml](https://storage.googleapis.com/google-code-attachments/selenium/issue-413/comment-2/seleniumTC2-1.html.xhtml)_
@lukeis

This comment has been minimized.

Copy link
Member Author

@lukeis lukeis commented Mar 2, 2016

Thanks for the reply. Please notice this issue was originally reported March 08 (more
than 10 months ago). Google instance was not out then, so the . Anyway, not important
to me anymore - used to a different position which does not use this product.


Reported by rahim.sayeef on 2011-02-01 05:48:28

@lukeis

This comment has been minimized.

Copy link
Member Author

@lukeis lukeis commented Mar 2, 2016

True; though the 'click' rather than 'click and wait' would have cause problems regardless.

Reported by adamgoucher on 2011-02-01 14:15:57

@lukeis

This comment has been minimized.

Copy link
Member Author

@lukeis lukeis commented Mar 2, 2016

Reported by luke.semerau on 2015-09-17 17:48:57

  • Labels added: Restrict-AddIssueComment-Commit
@lukeis lukeis closed this Mar 2, 2016
@SeleniumHQ SeleniumHQ locked and limited conversation to collaborators Mar 3, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.