anchor.diff:  For example:
   
   [source]
  +----
   test 'wip should render ...' do
     ...
   end
  +----
   
  -Then, run +ruby+ again, but this time pass a selector argument so it finds matching tests:
  +Then, run `ruby` again, but this time pass a selector argument so it finds matching tests:
   
    $ ruby test/blocks_test.rb -n /wip/
   
  -Once you are done with your test, make sure to remove "wip" from the description and run all the tests again using +rake+.
  +You can also turn on verbose mode if you want to see more output:
  +
  + $ ruby test/blocks_test.rb -n /wip/ -v
  +
  +Once you are done with your test, make sure to remove `wip` from the description and run all the tests again using `rake`.
   
   We plan on switching to a more elegant testing framework in the future, such as RSpec or Cucumber, in order to make the tests more clear and robust.
   
  
positive.code: == Submitting a Pull Request
  
  . {fork-help-uri}[Fork the repository].
  . Run +bundle install+ to install dependencies.
  . {branch-help-uri}[Create a topic branch].
  . Add tests for your unimplemented feature or bug fix. (See <<writing-and-executing-tests>>)
  . Run +bundle exec rake+ to run the tests.
  If your tests pass, return to step 3.
  . Implement your feature or bug fix.
  . Run +bundle exec rake+ to run the tests.
  If your tests fail, return to step 5.
  . Add documentation for your feature or bug fix.
  . If your changes are not 100% documented, go back to step 7.
  
negative.code: = Contributing
  // settings:
  :idprefix:
  :idseparator: -
  :source-language: ruby
  :language: {source-language}
  // URIs:
  :repo-uri: https://github.com/asciidoctor/asciidoctor
  :base-help-uri: https://help.github.com/articles
  :issues-uri: {repo-uri}/issues
  