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 3441270
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T08:31:57+00:00 2026-05-18T08:31:57+00:00

With Rspec 2 the rspeccommand is supposed to run the tests, replacing spec from

  • 0

With Rspec 2 the “rspec”command is supposed to run the tests, replacing “spec” from previous versions.
I tried running it on a new app and no tests were run (despite having a set of specs created). Regular rake spec works fine to run the tests so the issue is with the command

jack$ rspec

Finished in 0.00003 seconds
0 examples, 0 failures

Using Rails 3
rspec-2.0.1

Any ideas?

  • 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-18T08:31:58+00:00Added an answer on May 18, 2026 at 8:31 am

    you need to tell it where your specs are. Try

    rspec spec/
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm running rspec from within mvim with :!rspec spec/lib , however if I include
I am using rspec and cucumber to run watir tests at sauce labs. I
Every time I run RSpec tests, it goes off executing everything. Which is fine,
I'm new to RSpec and as I was writing a spec test I came
Rspec book says to run cucumber features -n command. But it is giving following
in my rails3 app I have installed rspec. But when I run the rspec
I'm running these rspec tests for my controller: require 'spec_helper' describe MoviesController do describe
In some Rspec model specs, we have several tests like this: it { should
I've been writing rspec + capybara tests for my application and came up with
In our rspec test for rails 3.1.0 app, we use both Factory.build and Factory.attributes_for.

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.