ward 0.1.0

data/.document

@@ -0,0 +1,5 @@
+README.markdown
+lib/**/*.rb
+bin/*
+features/**/*.feature
+LICENSE

data/.gitignore

@@ -0,0 +1,28 @@
+## MAC OS
+.DS_Store
+Icon*
+
+## TEXTMATE
+*.tmproj
+tmtags
+
+## EMACS
+*~
+\#*
+.\#*
+
+## VIM
+*.swp
+
+## RUBINIUS
+*.rbc
+
+## PROJECT::GENERAL
+.yardoc
+coverage
+doc
+measurements
+pkg
+rdoc
+
+## PROJECT::SPECIFIC

data/LICENSE

@@ -0,0 +1,19 @@
+Copyright (c) 2010 Anthony Williams
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.markdown

@@ -0,0 +1,99 @@
+# Ward
+
+_Ward is not ready for production use just yet. 0.1 should be considered a preview release only._
+
+## What Is It?
+
+Object validation inspired by RSpec. As it turns out, Ward looks very little like RSpec, but that's where the inspiration came from nonetheless.
+
+The aim is to provide an expressive DSL which allows you to compose validations without the need to create special validation methods.
+
+    class Person
+      include Ward::Validation
+
+      validate do |person|
+        person.subdomain.length.is(2..50)
+        person.has.at_least(5).posts
+        person.owner.name.is("Michael Scarn")
+      end
+    end
+
+Note: The syntax described above isn't currently supported, though you can achieve a very similar end result with 0.1:
+
+    class Person
+      cattr_accessor :validators
+
+      # ...
+    end
+
+    Person.validators = Ward::ValidationSet.build do |person|
+      person.subdomain.length.is(2..50)
+      person.has.at_least(5).posts
+      person.owner.name.is("Michael Scarn")
+    end
+
+    Person.validators.valid?(Person.new)
+    # => false
+
+    Person.validators.validate(Person.new)
+    # => Ward::Support::Result
+
+### Current Status & Roadmap
+
+**Planned for 0.2:**
+
+* Add the Ward::Validation module allowing for more conventional validation
+  (defining the validations _on_ the object to be validated, as is the case
+  with ActiveRecord and dm-validations).
+
+* Documentation is severely lacking, and will be improved. In the
+  meantime, Ward makes extensive use of Cucumber features (/features) where
+  you will find many examples of how to use the library in your own
+  applications.
+
+* Ward error messages are currently in English only, but full i18n support is
+  planned.
+
+**Planned for 0.3:**
+
+* Compatibility modules will be added to support at least ActiveRecord and
+  DataMapper; and perhaps Sequel and other ORMs after that, depending on
+  demand.
+
+**Later:**
+
+* The DSL is subject to change prior to 1.0.
+
+### Compatibility
+
+Ward specs are run against:
+
+  * Ruby (MRI) 1.8.6 p399,
+  * Ruby (MRI) 1.8.7 p249,
+  * Ruby (YARV) 1.9.1 p378,
+  * JRuby 1.4.0,
+  * Rubinius RC3.
+
+Ward depends on ActiveSupport 3.0 to provide support for inflections in error messages, and to add Ruby 1.9-style String interpolation. However, only the bare minimum is included from ActiveSupport in order to minimise the impact on your runtime environment (see `lib/ward.rb` for specifics).
+
+### Note on Patches/Pull Requests
+
+* Fork the project, taking care not to get any in your eyes.
+
+* Make your feature addition or bug fix.
+
+* Add tests for it. This is especially important not only because it helps
+  ensure that I don't unintentionally break it in a future version, but also
+  since it appeases Phyllis --- the goddess of Cucumbers --- who has been
+  known to rain showers of fresh vegetables on those who don't write tests.
+
+* Commit, but do not mess with the Rakefile, VERSION, or history. If you want
+  to have your own version, that is fine, but bump version in a commit by
+  itself so that I can ignore it when I pull.
+
+* Send me a pull request. Bonus points for topic branches. But we all know
+  everything is made up and the points don't matter.
+
+### Copyright
+
+Copyright (c) 2010 Anthony Williams, MIT Licensed.

data/Rakefile

@@ -0,0 +1,47 @@
+require 'rake'
+require 'rake/clean'
+
+require File.expand_path('../lib/ward/version', __FILE__)
+
+CLOBBER.include ['pkg', '*.gem', 'doc', 'coverage', 'measurements']
+
+begin
+  require 'jeweler'
+  Jeweler::Tasks.new do |gem|
+    gem.name        = 'ward'
+    gem.summary     = 'Ward'
+    gem.homepage    = 'http://github.com/antw/ward'
+    gem.description = 'Object validation inspired by RSpec.'
+
+    gem.author      = 'Anthony Williams'
+    gem.email       = 'hi@antw.me'
+
+    gem.platform    = Gem::Platform::RUBY
+    gem.has_rdoc    = false
+
+    # Dependencies.
+    gem.add_dependency 'activesupport', '>= 3.0.0.beta'
+
+    # Development dependencies.
+    gem.add_development_dependency 'rspec',     '>= 1.3.0'
+    gem.add_development_dependency 'cucumber',  '>= 0.3'
+    gem.add_development_dependency 'yard',      '>= 0.5'
+
+    gem.post_install_message =
+      "************************************************************\n" \
+      "\n" \
+      "Thank you for installing ward-#{Ward::VERSION}\n" \
+      "\n" \
+      "Please note that 0.1 is a preview release and considered\n" \
+      "unsuitable for use in a production environment.\n" \
+      "\n" \
+      "************************************************************\n" \
+  end
+
+  Jeweler::GemcutterTasks.new
+rescue LoadError
+  puts 'Jeweler (or a dependency) not available. Install it with: gem ' \
+       'install jeweler'
+end
+
+FileList['tasks/**/*.rake'].each { |task| import task }

data/VERSION

@@ -0,0 +1 @@
+0.1.0

data/features/acceptance_matcher.feature

@@ -0,0 +1,78 @@
+Feature: Acceptance matcher
+  In order to validate that a user has accepted an attribute
+  I want to be able to ensure collections have a certain number of members
+
+  Background:
+    Given a class with a 'terms' attribute
+
+  Scenario Outline: When the attribute value is accepted
+    When using a validation set like
+      """
+      object.terms.is.accepted
+
+      """
+    And the instance 'terms' attribute is '<value>'
+    Then the validation set should pass
+
+    Examples:
+      | value  |
+      | true   |
+      | "true" |
+      | "t"    |
+      | "yes"  |
+      | "y"    |
+      | 1      |
+      | "1"    |
+
+  Scenario Outline: When the attribute value is not accepted
+    When using a validation set like
+      """
+      object.terms.is.accepted
+
+      """
+    And the instance 'terms' attribute is '<value>'
+    Then the validation set should fail
+
+    Examples:
+      | value   |
+      | false   |
+      | nil     |
+      | ""      |
+      | "false" |
+      | "f"     |
+      | "no"    |
+      | "n"     |
+      | 0       |
+      | "0"     |
+
+  Scenario: When setting a single custom expectation value
+    When using a validation set like
+      """
+      object.terms.is.accepted("absolutely")
+
+      """
+    And the instance 'terms' attribute is 'absolutely'
+    Then the validation set should pass
+
+  Scenario: When setting a single custom expectation value and the attribute is not accepted
+    When using a validation set like
+      """
+      object.terms.is.accepted("absolutely")
+
+      """
+    And the instance 'terms' attribute is 'yes'
+    Then the validation set should fail
+
+  Scenario Outline: When setting several custom expectation values
+    When using a validation set like
+      """
+      object.terms.is.accepted(%w( absolutely certainly ))
+
+      """
+    And the instance 'terms' attribute is '<value>'
+    Then the validation set should pass
+
+    Examples:
+      | value      |
+      | absolutely |
+      | certainly  |

data/features/attribute_keyword.feature

@@ -0,0 +1,13 @@
+Feature: Validating objects with an "attribute" keyword
+  In order validate attributes whose name conflicts with DSL methods
+  I want to be able to use the attribute keyword
+
+  Scenario: With no arguments, a matcher, and a valid value
+    Given a class with a 'message' attribute
+    When using a validation set like
+      """
+      object.attribute(:message).is.equal_to('Wow! Signal')
+
+      """
+    And the instance 'message' attribute is 'Wow! Signal'
+    Then the validation set should pass

data/features/close_to_matcher.feature

@@ -0,0 +1,130 @@
+Feature: CloseTo matcher
+  In order to validate values which may vary slightly at runtime
+  I want to be able to use the close_to matcher to set an acceptable range of values
+
+  Background:
+    Given a class with an 'estimate' attribute
+
+  Scenario Outline: When the attribute value is within the specified integer delta
+    When using a validation set like
+      """
+      object.estimate.is.close_to(50, 10)
+
+      """
+    And the instance 'estimate' attribute is '<value>'
+    Then the validation set should pass
+
+    Examples:
+      | value |
+      | 40    |
+      | 50    |
+      | 55.0  |
+      | 60    |
+
+  Scenario Outline: When the attribute value is outside the specified integer delta
+    When using a validation set like
+      """
+      object.estimate.is.close_to(50, 10)
+
+      """
+    And the instance 'estimate' attribute is '<value>'
+    Then the validation set should fail
+      And the error on 'estimate' should be 'Estimate should be within 10 of 50'
+
+    Examples:
+      | value |
+      | 0     |
+      | 39    |
+      | 61    |
+
+  Scenario Outline: When the attribute value is within the specified float delta
+    When using a validation set like
+      """
+      object.estimate.is.close_to(2, 0.5)
+
+      """
+    And the instance 'estimate' attribute is '<value>'
+    Then the validation set should pass
+
+    Examples:
+      | value |
+      | 1.5   |
+      | 2     |
+      | 2.0   |
+      | 2.5   |
+
+  Scenario Outline: When the attribute value is outside the specified float delta
+    When using a validation set like
+      """
+      object.estimate.is.close_to(2, 0.5)
+
+      """
+    And the instance 'estimate' attribute is '<value>'
+    Then the validation set should fail
+      And the error on 'estimate' should be 'Estimate should be within 0.5 of 2'
+
+    Examples:
+      | value |
+      | 0     |
+      | 1.49  |
+      | 2.51  |
+
+  Scenario Outline: When the attribute value is a date inside the delta
+    When using a validation set like
+      """
+      object.estimate.is.close_to(Date.civil(2010, 3, 1), 1)
+
+      """
+    And the instance 'estimate' attribute is '<value>'
+    Then the validation set should pass
+
+    Examples:
+      | value |
+      | Date.civil(2010, 3, 1) - 1 |
+      | Date.civil(2010, 3, 1)     |
+      | Date.civil(2010, 3, 1) + 1 |
+
+  Scenario Outline: When the attribute value is a date outside the delta
+    When using a validation set like
+      """
+      object.estimate.is.close_to(Date.civil(2010, 3, 1), 1)
+
+      """
+    And the instance 'estimate' attribute is '<value>'
+    Then the validation set should fail
+      And the error on 'estimate' should be 'Estimate should be within 1 of 2010-03-01'
+
+    Examples:
+      | value |
+      | Date.civil(2010, 3, 1) - 2 |
+      | Date.civil(2010, 3, 1) + 2 |
+
+    Scenario Outline: When the attribute value is a date inside the delta
+      When using a validation set like
+        """
+        object.estimate.is.close_to(Time.parse('2010-03-01 12:00'), 30)
+
+        """
+      And the instance 'estimate' attribute is '<value>'
+      Then the validation set should pass
+
+      Examples:
+        | value |
+        | Time.parse('2010-03-01 12:00') - 30 |
+        | Time.parse('2010-03-01 12:00')      |
+        | Time.parse('2010-03-01 12:00') + 30 |
+
+    Scenario Outline: When the attribute value is a date outside the delta
+      When using a validation set like
+        """
+        object.estimate.is.close_to(Time.parse('2010-03-01 12:00'), 30)
+
+        """
+      And the instance 'estimate' attribute is '<value>'
+      Then the validation set should fail
+        And the error on 'estimate' should be '/^Estimate should be within 30 of/'
+
+      Examples:
+        | value |
+        | Time.parse('2010-03-01 12:00') - 31 |
+        | Time.parse('2010-03-01 12:00') + 31 |

data/features/context_arguments.feature

@@ -0,0 +1,47 @@
+Feature: Validating values which require an argument or block
+
+  Scenario: Supplying an argument to a context
+    Given the class has behaviour like
+      """
+      def name(yes = false)
+        if yes then "True" else "False" end
+      end
+
+      """
+    And using a validation set like
+      """
+      object.name(true).equal_to("True")
+
+      """
+    Then the validation set should pass
+
+  Scenario: Supplying an argument to a context when using scenarios
+    Given the class has behaviour like
+      """
+      def name(yes = false)
+        if yes then "True" else "False" end
+      end
+
+      """
+    And using a validation set like
+      """
+      object.name(true).equal_to("True")
+      object.name(false).equal_to("False").scenario(:negative)
+
+      """
+    Then the validation set should pass when using the 'negative' scenario
+
+  Scenario: Supplying a block to a context
+    Given the class has behaviour like
+      """
+      def name(&block)
+        block.call.reverse
+      end
+
+      """
+    And using a validation set like
+      """
+      object.name { "My value" }.equal_to("eulav yM")
+
+      """
+    Then the validation set should pass