Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7416215
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 29, 20262026-05-29T07:27:00+00:00 2026-05-29T07:27:00+00:00

It looks like those aliases are not loaded properly. I’m using Rails 3.X, rspec

  • 0

It looks like those aliases are not loaded properly. I’m using Rails 3.X, rspec 2.8 and capybara 1.1.2 to write some integration tests.
I think that my installation of Capybara is successful as it all works with the standard ‘describe’ and ‘it’ tags, but ‘feature’ and ‘scenario’ aliases from Capybara throw an ‘undefined method’ error.

I don’t see anything in the documentation mentioning more configuration:
https://github.com/jnicklas/capybara
I have simply added the ‘require capybara/rspec’ in my spec_helper.rb

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-29T07:27:01+00:00Added an answer on May 29, 2026 at 7:27 am

    It seems like you can’t combine describe/it with feature/scenario syntax. I was getting the same error when I nested a scenario block inside a describe block. Once I replaced the describe with feature, the test ran. One gotcha: It also does not seem to like nested feature blocks, which I guess makes sense in the context of acceptance testing.

    describe "some feature" do  # <== BAD
      scenario "some scenario" do
        #spec code here
      end
    end
    
    feature "some feature" do  # <== GOOD
      scenario "some scenario" do
        #spec code here
      end
    end
    

    UPDATE
    I dug into Capybara’s source code, and before and it don’t get aliased by background and scenario unless the describe block gets created with capybara_feature => true which happens when you create the block with feature instead of describe.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Looks like XSD.exe is not delivered as a part of Visual Studio 2010. what
Currently I am using a basic error controller which looks like this: class ErrorController
Looks like _compile_select is deprecated and get_compiled_select is not added to 2.1.0. Are there
I'm hoping to add events to some Google Flot charts, like those seen in
I'd like to create a table that looks like this: lolvalue---------|lol date|some other column
My collection looks like this I need to get all those order no's whose
i want to create a table : products which looks like (these are columns
You know how those packed js files look like, right? eval(function(p,a,c,k,e,d){ ... } ('obfuscated-string'.split('|'),0,{}))
Looks like while( condition ) { //do stuff } is completely equivalent to for(
Looks like ExpressionTrees compiler should be near with the C# spec in many behaviors,

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.