Permalink
Commits on Mar 27, 2010
  1. Version bump to 2010.0.2

    quackingduck committed Mar 27, 2010
  2. Version bump to 2010.0.1

    quackingduck committed Mar 27, 2010
  3. add -rubygems so tests run

    jonpliske committed Mar 27, 2010
Commits on Jan 6, 2010
  1. bugfix, the @example_file variable should only be set when `eg` is ca…

    quackingduck committed Jan 6, 2010
    …lled with an example, not when it is called to set helpers (which may happen in some shared environment/helper file)
Commits on Nov 21, 2009
  1. TWO THOUSAND AND TEN

    quackingduck committed Nov 21, 2009
  2. FANCY OUTPUT

    quackingduck committed Nov 21, 2009
    Without fancy:
    
      (s) version matches file:
        (s) version: |
          2000.2.0
      (s) errors are caught and nicely displayed:
        (s) result['status']: error
        (s) result['result']['class']: RuntimeError
        (s) result['result']['message']: boom!
        (s) result['result']['backtrace'][0]: examples/an_error.rb:4
      (s) check_output_matches_expected_for :no_checks:
        (s) output: |-
          - name: An example block without any checks prints the value of the block
            status: info (no checks)
            result: foo
      (s) check_output_matches_expected_for :oneliner:
        (s) output: |-
          - name: 1+2
            status: info (no checks)
            result: 3
      (s) check_output_matches_expected_for :no_checks_non_string:
        (s) output: |-
          - name: Non-string return values get converted to yaml
            status: info (no checks)
            result: !ruby/object:MyClass
              foo: bar
    
      ...etc
    
    With fancy:
    
      ✓ version matches file
      ✓ errors are caught and nicely displayed
      ✓ check_output_matches_expected_for :no_checks
      ✓ check_output_matches_expected_for :oneliner
      ✓ check_output_matches_expected_for :no_checks_non_string
    
    Essentially. The terminal output is pretty, uses ansi colors and is non-parsable, but when you call exemplor from something other than a terminal you're back to nice yaml
  3. Start of the output refactoring.

    quackingduck committed Nov 21, 2009
    Each example produces this rather verbose yaml as output:
    
        - name: Non-string return values get converted to yaml
          status: info (no checks)
          result: !ruby/object:MyClass
            foo: bar
    
    Previously it was:
    
        (i) Non-string return values get converted to yaml: !ruby/object:MyClass
          foo: bar
    
    While that was more concise it was more difficult to parse.
    
    Here's how it's going to work now:
    * When you run the examples from a terminal, you get fancy, colored, concise output.
    * When you run the examples from a non-terminal you get verbose, easy to parse yaml
    
    Ok. Now comes some refactoring. Then the fancy.
Commits on Nov 9, 2009
Commits on Nov 3, 2009
  1. [FIX] not a rake task

    quackingduck committed Nov 3, 2009
Commits on Oct 31, 2009
  1. works in theory

    quackingduck committed Oct 31, 2009
  2. Merge commit 'agrimm/master' into merge-agrimm

    quackingduck committed Oct 31, 2009
    Conflicts:
    	Rakefile
    	lib/exemplor.rb
Commits on Oct 30, 2009
  1. Version bump to 2000.1.0

    quackingduck committed Oct 30, 2009
  2. Version TWO THOUSAND!

    quackingduck committed Oct 30, 2009
Commits on Oct 29, 2009
  1. Version bump to 2.9.0

    quackingduck committed Oct 29, 2009
  2. [NEW] when run from a terminal, print what would have gone to STDERR …

    quackingduck committed Oct 29, 2009
    …to STDOUT after the example output
  3. [TODO] suggestion

    quackingduck committed Oct 29, 2009
Commits on Oct 27, 2009
  1. Fix 1.9 incompatibility.

    agrimm committed Oct 27, 2009
Commits on Oct 26, 2009