Sha256: ae013b6146179f80935162200e0648b4ae83cfaa9b2dd6418015bade8228e95e

Contents?: true

Size: 825 Bytes

Versions: 5

Compression:

Stored size: 825 Bytes

Contents

Feature: run with `ruby` command

  You can use the `ruby` command to run specs. You just need to require
  `rspec/autorun`.

  Generally speaking, you're better off using the `rspec` command, which avoids
  the complexity of `rspec/autorun` (e.g. no `at_exit` hook needed!), but some
  tools only work with the `ruby` command.

  Scenario: Require `rspec/autorun` from a spec file
    Given a file named "example_spec.rb" with:
      """ruby
      require 'rspec/autorun'

      RSpec.describe 1 do
        it "is < 2" do
          expect(1).to be < 2
        end

        it "has an intentional failure" do
          expect(1).to be > 2
        end
      end
      """
    When I run `ruby example_spec.rb`
    Then the output should contain "2 examples, 1 failure"
     And the output should contain "expect(1).to be > 2"

Version data entries

5 entries across 5 versions & 1 rubygems

Version Path
opal-rspec-1.1.0.alpha3 rspec-core/upstream/features/command_line/ruby.feature
opal-rspec-1.1.0.alpha2 rspec-core/upstream/features/command_line/ruby.feature
opal-rspec-1.1.0.alpha1 rspec-core/upstream/features/command_line/ruby.feature
opal-rspec-1.0.0 rspec-core/upstream/features/command_line/ruby.feature
opal-rspec-1.0.0.alpha1 rspec-core/upstream/features/command_line/ruby.feature