bug with using variable

[p0deje]

bug with using variable

[p0deje]

You have a typo in that line. It should be == not =.

[sergeych]

Sorry I put the wrong sample. and foget to escape <>. With '==' it gives the same error I'm trying to report and it is about m:

  1) Failure:
Boss#test_0001_Hash/Array keep the structure [/Users/sergeych/dev/boss_protocol/lib/boss-protocol.rb:99]:
--- expected
+++ actual
@@ -1 +1 @@
-true
+"#<NameError: undefined local variable or method `src' for Boss:Module>"

Please note that the problem is, executing the second line (src[1]) the src variable itself does not exist in the scope dove the test is being executed.

[p0deje]

I cannot reproduce the failure. I've added a simple test:

  Scenario: names test with example title when it's present
    Given a file named "doctest_helper.rb" with:
      """
      require 'app/app'
      """
    And a file named "app/app.rb" with:
      """
      # @example
      #   hash = {'foo' => 'bar'}
      #   src = hash
      #   src['foo'] == 'bar'
      #   #=> true
      #   src['foo'] == 'bar'
      #   #=> true
      def foo
      end
      """
    When I run `bundle exec yard doctest -v`
    Then the output should contain "1 runs, 2 assertions, 0 failures, 0 errors, 0 skips"

This scenario passes, so if you can provide a failure test case, that would be great.

Also, make sure you use the latest version of yard-doctest.

[sergeych]

try:

Feature: test doctest

Scenario: names test with example title when it's present
    Given a file named "doctest_helper.rb" with:
      """
      require 'app/app'
      """
    And a file named "app/app.rb" with:
      """
      module Test
      # @example
      #   hash = {'foo' => 'bar'}
      #   src = hash
      #   src['foo'] == 'bar'
      #   #=> true
      #   src['foo'] == 'bar'
      #   #=> true
      def foo
      end
      end
      """
    When I run `bundle exec yard doctest -v`
    Then the output should contain "1 runs, 2 assertions, 0 failures, 0 errors, 0 skips"

[p0deje]

Aha, I can reproduce it, thank you!

[p0deje]

This should be fixed in 0.1.10, please give it a shot!