Add MiniTest::Spec section in README.
This commit is contained in:
parent
6100a6a1d4
commit
6af5a5a7d7
11
README.rdoc
11
README.rdoc
|
@ -169,6 +169,17 @@ Test::Unit does not support selecting the driver through test metadata, but you
|
|||
can switch the driver for specific classes using the <tt>setup</tt> and
|
||||
<tt>teardown</tt> methods. See the section "Selecting the Driver".
|
||||
|
||||
== Using Capybara with MiniTest::Spec
|
||||
|
||||
Include Capybara::DSL like in Test::Unit. Be sure to include it in the proper class,
|
||||
which could be something other than ActionDispatch::IntegrationTest.
|
||||
|
||||
The capybara_minitest_spec gem ({Github}[https://github.com/ordinaryzelig/capybara_minitest_spec],
|
||||
{rubygems.org}[https://rubygems.org/gems/capybara_minitest_spec]) provides MiniTest::Spec
|
||||
expectations for Capybara. For example:
|
||||
|
||||
page.must_have_content('Important!')
|
||||
|
||||
== Using Capybara with Ruby on Rails
|
||||
|
||||
If you are using the Rails framework, add this line to automatically configure
|
||||
|
|
Loading…
Reference in New Issue