A crystal library for automatically testing documentation examples.

Docspec is crystal's equivalent of a doctest library.

• Docspec encourages documentation by creating tests from it.
• Docspec encourages testing by reducing boilerplate code for test cases.
• Docspec encourages fast development by reducing boilerplate code for test cases.

Add this to your application's shard.yml:

dependencies:
  docspec:
    github: skippi/docspec

Docspec parses source files for any commented codeblocks with code in them. For each codeblock line with a prefix of >>, it executes the line and stores the result. If the line also had an expression appended with # =>, then docspec will test that the result equals the appended expression.

Alternatively, you can use the [](@doctest) annotation instead of >> to mark entire codeblocks for doctesting.

In this example, we will fully doctest Foo.bar and Foo.baz, while ignoring doctesting for Foo.add. Note the usage of >> and [](@doctest):

# src/foo.cr

module Foo
  # Returns "hello world".
  #
  # ```
  # >> Foo.bar # => "hello world"
  #
  # >> name = "say #{Foo.bar}"
  # >> name # => "say hello world"
  # ```
  def self.bar
    "hello world"
  end

  # Subtracts two numbers.
  #
  # [](@doctest)
  # ```
  # Foo.baz(4, 2) # => 2
  # Foo.baz(-8, -4) # => -4
  # ```
  def self.baz(a, b)
    a - b
  end

  # Adds two numbers.
  #
  # ```
  # Foo.add(1, 3) # => 4
  # Foo.add(-2, -4) # => -6
  # ```
  def self.add(a, b)
    a + b
  end
end

Require docspec and doctest the source file using a relative path:

# spec/foo_spec.cr

require "docspec"

Docspec.doctest("../src/foo.cr")

Lastly, run your tests in your project's root directory.

crystal spec

• Official docs

1. Fork it ( https://github.com/skippi/docspec/fork )
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

• skippi - creator, maintainer