and it worked
@twalpole ok its passing now :)
@twalpole question you said something about transients does that make creating database stuff faster?
you can write your factories to accept the count of an association to create etc
(if you're not)
otherwise -- not much -- if you need to actually have the records accessible to the app then you need to create it
@boris-petrov I've looked - definitely appears to be an issue but I'm not sure whether it's really in the selenium visibility calculation or in the browser behavior. The issue is likely because a display: contents element doesn't actually generate a box of any size and so text contents would be assumed to be overflowing that non-box which should mean they would be hidden (logically). What the real behavior should be will require a careful reading of the CSS spec around display: contents
@boris-petrov I don't know whether that's a good assumption - from https://developer.mozilla.org/en-US/docs/Web/CSS/display - Current implementations in most browsers will remove from the accessibility tree any element with a display value of contents (but descendants will remain). This will cause the element itself to no longer be announced by screen reading technology. This is incorrect behavior according to the CSS specification.`
and from the CSS spec -https://www.w3.org/TR/css-display-3/#box-generation -
Note: As only the box tree is affected, any semantics based on the document tree, such as selector-matching, event handling, and property inheritance, are not affected. As of writing, however, this is not implemented correctly in major browsers, so using this feature on the Web must be done with care as it can prevent accessibility tools from accessing the element’s semantics.
I think this looks like a browser issue where the text really shouldn't be visible but is incorrectly shown by the browser
Is it possible to work with the browser's context menu? Actually I just need to know if it has appeared or not. Doing
page.driver.browser.action.context_click(find('video').native).perform does indeed open it but I can't seem to be able to work with it (via page.driver.browser.action.send_keys(:arrow_down).perform) or capture it in a screenshot. Any ideas?
has anyone had success with using spring or zeus to run a spec that uses capybara (and doing it quickly)? One of our applications takes ~30 seconds to boot puma and so there's a long feedback loop when iterating on system specs. It seems like I could write some tooling that manages keeping the test server up in the background and then overwrite
driver.needs_server? so capybara doesn't try to start one up? For context we use rspec / puma / selenium / firefox, but I don't think that would matter too much.
```
context 'cannot connect to redis' do
before { simulate_failed_connection }
it { logs_failed_connection }
it { is_expected.to be false }
end
how can in the simulate_failed_connection just raise a Redis::CannotConnectError
and remove a receive(stats)
I'm facing this kind of errors on my tests:
Failure/Error: visit("/channels/cf_internal/jobs/#{job.id}/editor_preview")
Capybara::Poltergeist::JavascriptError:
One or more errors were raised in the Javascript code on the page. If you don't care about these errors, you can ignore them by setting js_errors: false in your Poltergeist configuration (see documentation for details).
TypeError: undefined is not a function (evaluating 'window.addEvent')
TypeError: undefined is not a function (evaluating 'window.addEvent')
at http://127.0.0.1:35487/channels/cf_internal/jobs/64/editor_preview:28 in global code
# /usr/local/bundle/gems/poltergeist-1.17.0/lib/capybara/poltergeist/browser.rb:384:in `command'
# /usr/local/bundle/gems/poltergeist-1.17.0/lib/capybara/poltergeist/browser.rb:39:in `visit'
# /usr/local/bundle/gems/poltergeist-1.17.0/lib/capybara/poltergeist/driver.rb:99:in `visit'
# /usr/local/bundle/gems/capybara-2.4.4/lib/capybara/session.rb:227:in `visit'
# /usr/local/bundle/gems/capybara-2.4.4/lib/capybara/dsl.rb:51:in `block (2 levels) in <module:DSL>'
# ./spec/features/cml/multiple_spec.rb:20:in `block (2 levels) in <top (required)>'
Does anyone have a clue on how to fix it? It seems that the
window object is not available
@arthurnobrega Your problem is that
window.addEvent isn't defined - likely due to using JS in your assets that isn't support by Poltergeist which then prevents other JS from being executed when all your assets are combined into one by the asset pipeline. The real solution is to stop using poltergeist - it was obsolete 3 years ago - time to move to a newer driver
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