Sha256: a362c57bae97127f564a7247887e670284a52751e0de2413a3dc8a721fd38ada

Contents?: true

Size: 880 Bytes

Versions: 1

Compression:

Stored size: 880 Bytes

Contents

Feature: search_modules

  Most projects do not have a separate namespace for their classes, which the default that Bogus assumes. However, if all (or some) of your classes exist within some module you can add it to the list of modules that Bogus will look in when trying to resolve class names.

  Scenario: search_modules
    Given a file named "foo.rb" with:
    """ruby
    class Foo
      def foo
      end
    end

    module Bar
      class Baz
        def baz
        end
      end
    end
    """

    Then spec file with following content should pass:
    """ruby

    Bogus.configure do |c|
      c.search_modules << Bar
    end

    describe "logger class fake" do
      fake(:foo)
      fake(:baz)

      it "finds classes in global namespace" do
        foo.foo
      end

      it "finds classes in specified modules" do
        baz.baz
      end
    end
    """


Version data entries

1 entries across 1 versions & 1 rubygems

Version Path
bogus-0.1.0 features/configuration/search_modules.feature