Ive updated to gem webdrivers and the latest chromedriver as well
driver = Capybara::Selenium::Driver.new(app, browser: :chrome, options: options)
or check whether $ exists before using it
@twalpole - I have in a test
click_on(exact_text: /\w{48}\.txt/). Before that I do a "search" in my app which returns one result (the one that must be clicked). But Capybara tells me Ambiguous match, found 38 elements matching visible link or button nil. This is definitely not correct. There is only one link that has that exact text. If I get the HTML that is produced by the failure and put it in a simple test case, it passes. Capybara does something strange. If I change it to click_on(text: /\w{48}\.txt/) it works fine. This is using Capybara.exact = false. Any ideas?
Also, if I put a
sleep 1 before that, it passes too.
@boris-petrov Not 100% sure -- there are some speed optimizations that are done which may be behaving incorrectly here due to the nil selector. Do you have
default_max_wait_time set to a very small value? Workarounds could possibly be click_on(text: /^\w{48}\.txt$/) or click_on(text: /\w{48}\.txt/, exact_text: true)
No, my default wait time is 10 seconds so it's definitely not small. Thanks for the workarounds! They probably work but is this something you want to take a look into as a fix in Capybara or you don't think it's worth it? Unfortunately I can't seem to be able to create a reproduction. :(
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/selenium-webdriver-4.1.0/lib/selenium/webdriver/remote/bridge.rb:57:in `create_session'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/selenium-webdriver-4.1.0/lib/selenium/webdriver/common/driver.rb:340:in `create_bridge'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/selenium-webdriver-4.1.0/lib/selenium/webdriver/common/driver.rb:74:in `initialize'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/selenium-webdriver-4.1.0/lib/selenium/webdriver/common/driver.rb:47:in `new'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/selenium-webdriver-4.1.0/lib/selenium/webdriver/common/driver.rb:47:in `for'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/selenium-webdriver-4.1.0/lib/selenium/webdriver.rb:88:in `for'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/capybara-3.36.0/lib/capybara/selenium/driver.rb:83:in `browser'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/capybara-3.36.0/lib/capybara/selenium/driver.rb:104:in `visit'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/capybara-3.36.0/lib/capybara/session.rb:278:in `visit'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/capybara-3.36.0/lib/capybara/dsl.rb:53:in `call'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/capybara-3.36.0/lib/capybara/dsl.rb:53:in `visit'
/home/derrell/RubymineProjects/AliasMadness/features/step_definitions/login.step_definition.rb:22:in `nil'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/cucumber-7.1.0/lib/cucumber/glue/invoke_in_world.rb:26:in `cucumber_instance_exec_in'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/cucumber-7.1.0/lib/cucumber/glue/step_definition.rb:133:in `invoke'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/cucumber-7.1.0/lib/cucumber/step_match.rb:33:in `invoke'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/cucumber-7.1.0/lib/cucumber/step_match.rb:26:in `block in activate'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/cucumber-core-10.1.1/lib/cucumber/core/test/action.rb:23:in `execute'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/cucumber-core-10.1.1/lib/cucumber/core/test/step.rb:35:in `execute'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/cucumber-core-10.1.1/lib/cucumber/core/test/runner.rb:106:in `execute'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/cucumber-core-10.1.1/lib/cucumber/core/test/runner.rb:53:in `execute'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/cucumber-core-10.1.1/lib/cucumber/core/test/runner.rb:29:in `test_step'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/cucumber-core-10.1.1/lib/cucumber/core/test/step.rb:23:in `describe_to'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/cucumber-core-10.1.1/lib/cucumber/core/test/case.rb:31:in `block (3 levels) in describe_to'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/cucumber-core-10.1.1/lib/cucumber/core/test/case.rb:30:in `each'
/home/derrell/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/cucumber-core-10.1.1/lib/cucumber/core/test/case.rb:30:in `block (2 levels) in describe_to'That's my stack trace. I have numerous errors, and they all start with a Capybara#visit call. I suspect they're the first such call in each flow (it will take some time to check that, if it's relevant). I have just upgraded gems for ruby 2.7.5 from 2.6.?. Upgrading ruby and just doing bundle install wasn't enough to trigger this error, but in attempting to push to heroku, I kept having issues with the asset pipeline, and had to upgrade mini_racer, and thus all of the stuff in the test gems to be sure it was working as it would. Now my tests fail, and I am hoping it's just webdriver and not something deep in my code.
This is Rails 6 latest.
Recruit security technicians, high salary, monthly salary can be as high as 50,000 US dollars
job requirements:
job requirements:
- Work experience in security industry
- Possess the practical ability of WEB/APP penetration testing
- Familiar with security testing tools such as kali linux, awvs, nessus, metasploit, burpsuite, etc., and have a certain understanding of their principles
- Familiar with at least one programming language, such as Python, Java, etc.
- Familiar with industry security attack and defense trends, track the latest security vulnerabilities, be able to analyze vulnerability principles and implement PoC
- Familiar with common web security vulnerabilities, business logic vulnerabilities and their principles in OWASP
Recruit security technicians, high salary, monthly salary can be as high as 50,000 US dollars
job requirements:
job requirements:
- Work experience in security industry
- Possess the practical ability of WEB/APP penetration testing
- Familiar with security testing tools such as kali linux, awvs, nessus, metasploit, burpsuite, etc., and have a certain understanding of their principles
- Familiar with at least one programming language, such as Python, Java, etc.
- Familiar with industry security attack and defense trends, track the latest security vulnerabilities, be able to analyze vulnerability principles and implement PoC
- Familiar with common web security vulnerabilities, business logic vulnerabilities and their principles in OWASP
Contact: Email: zhouchaoxian88gmail.com
in my case the replace text is already selecteed. find_field(class: 'js-ad-bill-message').send_keys("50") worked in replacing just that.
@twalpole I believe Capybara has a bug when used with Selenium 4.3.0. A test of mine started failing after updating Selenium's version. Capybara is the latest. The specific code that is not working right is
find('.foobar').click(x: 120, y: 10). When running on Selenium 4.2.1, this code works fine. I do see a warning however - WARN Selenium moving to an element with offset currently tries to use the top left corner of the element as the origin; in Selenium 4.3 it will use the in-view center point of the element as the origin. - which comes exactly from that line. I guess that is related to the problem?
I should have checked the changelog before writing here. Sorry about that!
I want to access the
example.metadata or example.example_group.before_context_ivars or something.
No. The current example is an RSpec construct. It’s passed to the blocks passed to a number of the RSpec methods (it, let, before, after, etc). If you want to access it later you could store that in an instance variable like anything else you want accessible in other methods
@boris-petrov
have_no_text isn't defined to work with an array, and I would be shocked if it did. It'll call to_s on the array and then verify that your page doesn't have whatever that string equivalent of the array is. I also wonder why you'd think what have_no_text accepts would have any relevance on what have_no_css accepts?
If you want multiple selector support you should look at
have_none_of_selectors - https://rubydoc.info/github/teamcapybara/capybara/Capybara/RSpecMatchers#have_none_of_selectors-instance_method
hm, so I've been using
have_no_text in the wrong way for a while! :D Thankfully just in one place. have_none_of_selectors doesn't seem to fit exactly what I need I believe - I want to check that something doesn't contain any of the strings that I pass - for example expect(page).to have_no_text(['foo', 'bar', 'baz']) - i.e. I want the current scope to not contain either of the three strings. I'm not sure that's possible with have_none_of_selectors? Perhaps that could be a feature request. :)
2 replies
I am seeing more usage of aria-disabled for elements like buttons and fields, etc. recently. While testing for some_button.disabled?, I get false when the button is disabled via aria-disabled. If the element just has the vanilla disabled attribute, that same element registers as disabled. Is there some setting needed for capybara to handle aria-disabled and treat it as disabled when true? Currently using "3.35.3". Would a newer version handle this? Thanks.