FAQ
*Tools Used:*

*Scripting Language :* Ruby
*BDD :* RSpec
*Browser Automation* : Selenium Webdriver
*Parallelization: *Selenium Grid and deep_test


- *Launched Hub :* java -jar selenium-server-standalone-2.22.0.jar -role
hub -timeout=30 -browserTimeout=60 -maxSession=20 -maxInstances=20
- *Launched Remote Control *: java -jar
selenium-server-standalone-2.22.0.jar -role node -hub
http://localhost:4444/grid/register -maxSession=20 -port=5555
- *DeepTest in rake file*:

*desc "Run_all_tests_in_parallel_using_deep_test"*
* Spec::Rake::SpecTask.new("tests:run_in_parallel") do |t|*
* t.spec_files = FileList["spec/*_spec.rb"]*
* t.deep_test :number_of_workers =>5,*
* :timeout_in_seconds =>300*
* end*
*
*
* task :default => :'tests:run_in_parallel'*
* *
Using the above tools and configurations, I am able to execute tests in
parallel which I am very happy about.
But the problem is my tests randomly keeps failing.

The DOM looks something likes this:

*<div class='sign_in_box'>*
* <form accept-charset="UTF-8" action="/en/user_sessions" method="post">*
* <div style="margin:0;padding:0;display:inline">*
* <input name="utf8" type="hidden" value="&#x2713;" />*
* <input name="authenticity_token" type="hidden"
value="05GXeEyUgx9f9EV225Am6LuRiKe/M9NpgqNRv9K0DYM=" />*
* </div> *
* <label for="user_session_email">E-mail Address</label>**
*
* **<br>*
* **<input id="user_session_email" name="user_session[email]" title="email
address" type="text" />*
* **<br>*
* **<br>*
* **<label for="user_session_password">Password</label>*
* <br>*
* **<input class="swappable_field" id="faker" name="faker" type="text"
value="password" />*
* **<div class='additional_links'>*
* **<input class="swapped_field" id="user_session_password"
name="user_session[password]" style="display: none" type="password" />*
* ......... *

The code I use to log in to this page

- This works fine when tests run sequentially.
- Sometimes when run parallely

@driver.find_element("id","user_session_email").send_keys value
@driver.find_element("id", "faker").clear
@driver.find_element("id", "user_session_password").send_keys value

I tried everything I could google for, wait_for_page_to_load,
wait_for_element, even simple wait and sleep, tests still randomly fails
And it says

Selenium::WebDriver::Error::ElementNotVisibleError in 'ClupSearch
test_listed_dental_services'
Element is not currently visible and so may not be interacted with
Command duration or timeout: 9 milliseconds

The element that it fails to identify is "user_session_password". (Always).

Is it really something specific to grid.... something tells me that there
exists a small fix to this issue.

I honestly dont want to give up after doing so much hard work on grid and
deep_test.

Let me know if you have any other information.

Thanks in advance.






--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To post to this group, send email to selenium-users@googlegroups.com.
To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/Ps5fAj2ZfbkJ.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

  • Peter Gale at Jul 20, 2012 at 8:08 am
    Hi

    Unless someone just happens to know something that might be relevant to your situation, I think we need details of a concrete example of failure. i.e. the full actual html at the time of a failure, the command being executed and a screenshto woudl be nice.

    Peter

    Date: Thu, 19 Jul 2012 11:32:23 -0700
    From: khushiy@gmail.com
    To: selenium-users@googlegroups.com
    Subject: [selenium-users] Selenium Grid, Selenium Webdriver and deep_test question.

    Tools Used:
    Scripting Language : RubyBDD : RSpecBrowser Automation : Selenium WebdriverParallelization: Selenium Grid and deep_test
    Launched Hub : java -jar selenium-server-standalone-2.22.0.jar -role hub -timeout=30 -browserTimeout=60 -maxSession=20 -maxInstances=20 Launched Remote Control : java -jar selenium-server-standalone-2.22.0.jar -role node -hub http://localhost:4444/grid/register -maxSession=20 -port=5555DeepTest in rake file: desc "Run_all_tests_in_parallel_using_deep_test" Spec::Rake::SpecTask.new("tests:run_in_parallel") do |t| t.spec_files = FileList["spec/*_spec.rb"] t.deep_test :number_of_workers =>5, :timeout_in_seconds =>300 end
    task :default => :'tests:run_in_parallel' Using the above tools and configurations, I am able to execute tests in parallel which I am very happy about.But the problem is my tests randomly keeps failing.
    The DOM looks something likes this:
    <div class='sign_in_box'>
    <form accept-charset="UTF-8" action="/en/user_sessions" method="post"> <div style="margin:0;padding:0;display:inline"> <input name="utf8" type="hidden" value="✓" /> <input name="authenticity_token" type="hidden" value="05GXeEyUgx9f9EV225Am6LuRiKe/M9NpgqNRv9K0DYM=" /> </div> <label for="user_session_email">E-mail Address</label>
    <br> <input id="user_session_email" name="user_session[email]" title="email address" type="text" /> <br> <br> <label for="user_session_password">Password</label> <br> <input class="swappable_field" id="faker" name="faker" type="text" value="password" /> <div class='additional_links'> <input class="swapped_field" id="user_session_password" name="user_session[password]" style="display: none" type="password" /> .........
    The code I use to log in to this page This works fine when tests run sequentially.Sometimes when run parallely@driver.find_element("id","user_session_email").send_keys value
    @driver.find_element("id", "faker").clear
    @driver.find_element("id", "user_session_password").send_keys value

    I tried everything I could google for, wait_for_page_to_load, wait_for_element, even simple wait and sleep, tests still randomly failsAnd it says
    Selenium::WebDriver::Error::ElementNotVisibleError in 'ClupSearch test_listed_dental_services'Element is not currently visible and so may not be interacted withCommand duration or timeout: 9 milliseconds
    The element that it fails to identify is "user_session_password". (Always).
    Is it really something specific to grid.... something tells me that there exists a small fix to this issue.
    I honestly dont want to give up after doing so much hard work on grid and deep_test.
    Let me know if you have any other information.
    Thanks in advance.









    --

    You received this message because you are subscribed to the Google Groups "Selenium Users" group.

    To post to this group, send email to selenium-users@googlegroups.com.

    To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.

    To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/Ps5fAj2ZfbkJ.

    For more options, visit https://groups.google.com/groups/opt_out.






    --
    You received this message because you are subscribed to the Google Groups "Selenium Users" group.
    To post to this group, send email to selenium-users@googlegroups.com.
    To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupselenium-users @
categoriesselenium
postedJul 20, '12 at 7:42a
activeJul 20, '12 at 8:08a
posts2
users2
websiteseleniumhq.org

2 users in discussion

Khushboo yadav: 1 post Peter Gale: 1 post

People

Translate

site design / logo © 2022 Grokbase