Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>after installing the rspec and cucumber you must run following commands </p> <p><strong>rails generate rspec:install</strong> for rspec</p> <p>first command will configure rails generate command and it will create the spec directory which will contain tests for your models, controllers, views in respective directory you can write the rspec test</p> <p>eg. If you are having user model then specs for user will go in</p> <p><strong>spec/models/user_spec.rb</strong> </p> <p>that's it</p> <p>to run these tests use</p> <p><strong>rspec spec/models/user_spec.rb</strong></p> <p>which will output the whether the tests are passed or not</p> <p>cucumber describes the behavior of application </p> <p>and rspec describes behavior of object </p> <p><em><strong>rails generate cucumber:install</em></strong> for cucumber</p> <p>which will create features directory in your application root</p> <p>inside that you can write cucumber test with .feature extension </p> <p>eg. If your application have feature like creating user, this feature will go in</p> <p>features/creating_user.feature file</p> <p>and the step definition for this feature will go in</p> <p>features/step_definitions/create_user_steps.rb</p> <p>well its just short guide line you can refer the following links</p> <p>for cucumber <strong><a href="http://loudcoding.com/posts/quick-tutorial-starting-with-cucumber-and-capybara-bdd-on-rails-project/" rel="nofollow">http://loudcoding.com/posts/quick-tutorial-starting-with-cucumber-and-capybara-bdd-on-rails-project/</a></strong> </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload