Databases
StackOverflow2013
Postsdbo
POHow to suppress noise from requests when running Rspec feature specs?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to suppress noise from requests when running Rspec feature specs?
    primarykey
    data
    text
    <p>I'm using Rspec feature specs and when I run them I get output such as:</p> <pre><code>.............Started GET "/sign_up" for 127.0.0.1 at 2013-08-08 10:52:00 -0700 Started POST "/accounts" for 127.0.0.1 at 2013-08-08 10:52:01 -0700 Started GET "/" for 127.0.0.1 at 2013-08-08 10:52:01 -0700 .Started GET "/sign_in" for 127.0.0.1 at 2013-08-08 10:52:02 -0700 Started POST "/users/sign_in" for 127.0.0.1 at 2013-08-08 10:52:02 -0700 Started GET "/" for 127.0.0.1 at 2013-08-08 10:52:02 -0700 ................................. (etc...) </code></pre> <p>How can I suppress the messages from the requests in my output? I've tried setting log levels to no avail. Any ideas would be appreciated. Thanks!</p> <h3>Edit:</h3> <p>This is a Rails 4 project using Ruby 2.0.</p> <p>spec/spec_helper.rb</p> <pre><code>ENV["RAILS_ENV"] ||= 'test' require File.expand_path("../../config/environment", __FILE__) require 'rspec/rails' require 'rspec/autorun' require 'factory_girl' require 'capybara/rails' require 'capybara/rspec' require 'webmock/rspec' Dir[Rails.root.join("spec/support/**/*.rb")].each { |f| require f } ActiveRecord::Migration.check_pending! if defined?(ActiveRecord::Migration) RSpec.configure do |config| config.mock_with :mocha config.include FactoryGirl::Syntax::Methods config.use_transactional_fixtures = true config.infer_base_class_for_anonymous_controllers = false config.order = "random" end </code></pre> <p>spec/features/sign_in_spec.rb</p> <pre><code>require "spec_helper" feature "Sign in" do background do account = create(:account) @admin = account.admin end scenario "User signs into the application" do visit sign_in_path fill_in "user_email", with: @admin.email fill_in "user_password", with: @admin.password click_button "Sign in" expect(page).to have_content "Signed in successfully" end end </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USuser1647525
    1. USuser1647525
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to suppress noise from requests when running Rspec feature specs?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to suppress noise from requests when running Rspec feature specs?
      1. USKyle Tolle
      1. VTFavorite
    3. VO
      singulars
      1. POHow to suppress noise from requests when running Rspec feature specs?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPlease show us your `spec_helper` and one of your `spec`
      singulars
      1. POHow to suppress noise from requests when running Rspec feature specs?
      1. USPierre-Louis Gottfrois
    2. COI've added what you requested. This is a fairly new Rails 4 (Ruby 2.0) project, so there isn't really anything fancy going on. Thanks for any suggestions.
      singulars
      1. POHow to suppress noise from requests when running Rspec feature specs?
      1. USuser1647525
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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