The step we used in the past (Then "foo" should not be visibile) doesn't reliably work in Selenium features.
I overhauled the entire step so it uses Javascript to detect visibility in Selenium.
The step has support for jQuery and Prototype projects, so it should be a drop-in replacement for all your projects.
For Rack::Test the step no longer uses XPath so you should be able to understand it when you are not a cyborg :)
There were some other cards detailing alternative steps to detect visibility. I deleted all these other cards since the updated step should work in all situations. If you find a problem with the updated step, please work with me to maintain it. We should only have one standard step for the same thing.

makandracards.com

Henning Koch

makandra.com

Say thanks

Last edit

Almost 12 years ago

License

Source code in this card is licensed under the MIT License.

Async control flow in JavaScript: Promises, Microtasks, async/await

Slides for Henning's talk on Sep 21st 2017.

Understanding sync vs. async control flow

Talking to synchronous (or "blocking") API

print('script start')
html = get('/foo')
print(html)
print('s...

Delivering Carrierwave attachments to authorized users only

Preparation

To attach files to your records, you will need a new database column representing the filename of the file. To do this, add a new migration (rails g migration <name>) with the following content:

class AddAttachmentToNotes...

Posted by Henning Koch to makandra dev (2012-07-18 08:54)

Updated: Capybara: Check that a page element is hidden via CSS

Related cards:

Summary

Understanding sync vs. async control flow

Talking to synchronous (or "blocking") API

Introduction

Preparation