Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Having issues with tests timing out #1

Open
brobertsaz opened this issue Jan 1, 2013 · 4 comments
Open

Having issues with tests timing out #1

brobertsaz opened this issue Jan 1, 2013 · 4 comments

Comments

@brobertsaz
Copy link

First off, I love this gem!!! I am having issues with the tests timing out. I have added in sleep 2's before and after the action button clicks but it is still hanging up during tests basically after it prints out:

<Capybara::Element tag="div">

Any ideas?

BR
@goodwill
Copy link
Owner

goodwill commented Jan 2, 2013

Could provide a simple test case so I could know what exactly causing the
timeout? I know the gem has a very limited coverage on how it should work
on various scenario (I just extract this from what I did, so surely it
needs a bit more work to cover more cases), thanks in advance.

On Tue, Jan 1, 2013 at 12:42 PM, Bob Roberts notifications@git.luolix.topwrote:

First off, I love this gem!!! I am having issues with the tests timing
out. I have added in sleep 2's before and after the action button clicks
but it is still hanging up during tests basically after it prints out:

Any ideas?

BR

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1.

Regards,

William Yeung

Consultant

jquery+rubyonrails

Tofugear

E: william@tofugear.com
T: +852 21519830
M: +852 92538475
W: http://tofugear.com

@brobertsaz
Copy link
Author

OK, I forked and removed the pretty print but that made no change. What I have found is occurring when there are multiple select2 drop downs in a test. I see that the tests are passing but Rspec seems to miss it.

So far a workaround is to use a fill_in or something else after the last select2.

@goodwill
Copy link
Owner

goodwill commented Jan 8, 2013

The way I did mine is based on the situation I am applying select2 on a dropdown, not sure if your scenario is the same?

On 8 Jan, 2013, at 8:09 AM, Bob Roberts notifications@github.com wrote:

OK, I forked and removed the pretty print but that made no change. What I have found is occurring when there are multiple select2 drop downs in a test. I see that the tests are passing but Rspec seems to miss it.

So far a workaround is to use a fill_in or something else after the last select2.

—
Reply to this email directly or view it on GitHub.

@brobertsaz
Copy link
Author

Yes I am using them for drop downs.

akarzim pushed a commit to akarzim/capybara-select2 that referenced this issue Oct 15, 2013
@sanvuthy
Merge pull request goodwill#1 from chanthou/master
8313905 
update select2_multiple to find by xpath
p-salido referenced this issue in p/capybara-select2 Dec 19, 2017
@p
Merge remote-tracking branch 'Hirurg103/master'
cb66d38 
* Hirurg103/master:
  Fix `found 2 elements matching css: input.select2-input` when there are two select2 elements with multiple selection
  Fix typo
  Add support to add tags for select2 version 3.5.2
  Fix backward compatibility with select2 <v4.0 when search is specified [Fix goodwill#51]
  Click on the search field to open multiple select box
  Fix issue with large usage of time to find and select an option [Fixes #1]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@goodwill @brobertsaz