capybara-ui

capybara-ui copied to clipboard

Improve `see` error message

3

Currently the error message can be a bit misleading. "Unable to see your_widget and my-class". If the widget is defined in part by the class, the error message would be...

adsteel

Rename relishapp to capybara-ui, or delete it

1

adsteel

This is a problem if one is using a widget to get the actual value attribute. ``` bash widget(:my_input).value => "" widget(:my_input).root.value => "My value" ```

adsteel

A recent change breaks usage on Rails using the `rspec-rails` gem, but tests could not catch it.

adsteel

This custom RSpec step would minimize awkwardness from being forced to find ways to make :see work. e.g. ``` expect(roles.user).to be :in_edit_mode vs expect(roles.user).to see :edit_mode_enabled ``` ``` def is_in_edit_mode?...

adsteel

http://www.rubydoc.info/github/jnicklas/capybara/Capybara%2FNode%2FActions%3Aattach_file

adsteel

http://www.rubydoc.info/github/jnicklas/capybara/Capybara/Node/Element#drag_to-instance_method e.g. `widget(:item).drag_to(widget(:item_list_top))`

adsteel

Widgets in the top namespace should be visible to other widgets using #widget

4

They will be automatically scoped to the current widget

david

document default_locator

2

shoe

item_factory should not be stored as class ivar, because its value then fails to propagate to subclasses

2

david