ward 0.1.0

data/features/equal_to_matcher.feature

@@ -0,0 +1,25 @@
+Feature: EqualTo matcher
+  In order to validate that an exact value
+  I want to be able to use the equal_to matcher to set the expected value
+
+  #
+  # The equal_to keyword can often be removed in favour of using +is+ with a
+  # value. See is_keyword.feature for examples.
+  #
+
+  Background:
+    Given a class with an 'name' attribute
+    And using a validation set like
+      """
+      object.name.is.equal_to('Michael Scarn')
+
+      """
+
+  Scenario: When the attribute value matches the expected value
+    When the instance 'name' attribute is 'Michael Scarn'
+    Then the validation set should pass
+
+  Scenario: When the attribute value does not match the expected value
+    When the instance 'name' attribute is 'Michael Scott'
+    Then the validation set should fail
+      And the error on 'name' should be 'Name should be Michael Scarn'

data/features/error_messages.feature

@@ -0,0 +1,69 @@
+Feature: Error messages when a validation fails
+  In order to provide useful information when a validation fails
+  I want to be able to retrieve a list of nicely worded error messages
+  So that descriptive messages which describe the errors can be displayed
+
+  Background:
+    Given a class with a 'name' attribute
+
+  Scenario: When validating an attribute of the object
+    When using a validation set like
+      """
+      object.name.is.present
+
+      """
+    When the instance 'name' attribute is ''
+    Then the error on 'name' should be 'Name should be present'
+
+  Scenario: When validating the object itself
+    When using a validation set like
+      """
+      object.is_not.present
+
+      """
+    Then the error on 'base' should be 'Should not be present'
+
+  Scenario: Interpolating extra values from the matcher
+    When using a validation set like
+      """
+      object.name.has(1).character
+
+      """
+    When the instance 'name' attribute is ''
+    Then the error on 'name' should be 'Name should have 1 character'
+
+  Scenario: When the matcher indicates a specific error key
+    When using a validation set like
+      """
+      object.name.has.between(1..5).characters
+
+      """
+    When the instance 'name' attribute is ''
+    Then the error on 'name' should be 'Name should have between 1 and 5 characters'
+
+  Scenario: Providing a custom error when the validation is defined
+    When using a validation set like
+      """
+      object.name.is.present.message('Whoops!')
+
+      """
+    When the instance 'name' attribute is ''
+    Then the error on 'name' should be 'Whoops!'
+
+  Scenario: Providing a custom error with interpolation
+    When using a validation set like
+      """
+      object.name.is.present.message('%{context} had a whoopsie')
+
+      """
+    When the instance 'name' attribute is ''
+    Then the error on 'name' should be 'Name had a whoopsie'
+
+  Scenario: Providing a custom name for the context
+    When using a validation set like
+      """
+      object.name.is.present.context('you')
+
+      """
+    When the instance 'name' attribute is ''
+    Then the error on 'name' should be 'You should be present'

data/features/external_validation.feature

@@ -0,0 +1,15 @@
+Feature: Validating objects without "include"ing any modules
+  In order to reduce the impact on a user's environment
+  I want to be able to validate an object which knows nothing about Ward
+
+  Background:
+    Given a class with a 'name' attribute
+    When validating the 'name' attribute
+
+  Scenario: Passing validation
+    When the instance 'name' attribute is valid
+    Then the validation set should pass
+
+  Scenario: Failing validation
+    When the instance 'name' attribute is invalid
+    Then the validation set should fail

data/features/has_matcher.feature

@@ -0,0 +1,72 @@
+Feature: Has matcher
+  In order to validate the length of a collection
+  I want to be able to ensure collections have a certain number of members
+
+  Background:
+    Given a class with a 'posts' attribute
+
+  Scenario: When validating with a collection name and the correct member size
+    When using a validation set like
+      """
+      object.has(2).posts
+
+      """
+    When the instance 'posts' attribute is '[1, 2]'
+    Then the validation set should pass
+
+  Scenario: When validating with a collection name and an incorrect member size
+    When using a validation set like
+      """
+      object.has(2).posts
+
+      """
+    When the instance 'posts' attribute is '[1]'
+    Then the validation set should fail
+      And the error on 'base' should be 'Should have 2 posts'
+
+  Scenario: When validating without a collection name and the correct member size
+    When using a validation set like
+      """
+      object.posts.has(2)
+
+      """
+    When the instance 'posts' attribute is '[1, 2]'
+    Then the validation set should pass
+
+  Scenario: When validating without a collection name and an incorrect member size
+    When using a validation set like
+      """
+      object.posts.has(2)
+
+      """
+    When the instance 'posts' attribute is '[1]'
+    Then the validation set should fail
+      And the error on 'posts' should be 'Posts should have 2 items'
+
+  Scenario: When validating without a non-responding collection name and the correct member size
+    When using a validation set like
+      """
+      object.posts.has(2).members
+
+      """
+    When the instance 'posts' attribute is '[1, 2]'
+    Then the validation set should pass
+
+  Scenario: When validating without a non-responding collection name and an incorrect member size
+    When using a validation set like
+      """
+      object.posts.has(2).members
+
+      """
+    When the instance 'posts' attribute is '[1]'
+    Then the validation set should fail
+      And the error on 'posts' should be 'Posts should have 2 members'
+
+  Scenario: When using a singular collection name and the value responds to the plural
+    When using a validation set like
+      """
+      object.has(1).post
+
+      """
+    When the instance 'posts' attribute is '[1]'
+    Then the validation set should pass

data/features/has_matcher_initialized_with_expectation.feature

@@ -0,0 +1,94 @@
+Feature: Has matcher when initialized with an expected length
+  In order allow the has matcher to read more like a natural language
+  I want to be able to initialize the matcher with an expectation
+
+  Background:
+    Given a class with a 'posts' attribute
+
+  Scenario: Initialized with an exact value and the correct member size
+    When using a validation set like
+      """
+      object.has(2).posts
+
+      """
+    When the instance 'posts' attribute is '[1, 2]'
+    Then the validation set should pass
+
+  Scenario: Initialized with an exact value and an incorrect member size
+    When using a validation set like
+      """
+      object.has(2).posts
+
+      """
+    When the instance 'posts' attribute is '[1]'
+    Then the validation set should fail
+
+  Scenario Outline: Initialized with no value and a member size > 0
+    When using a validation set like
+      """
+      object.has.posts
+
+      """
+    When the instance 'posts' attribute is '<posts>'
+    Then the validation set should pass
+
+    Examples:
+      | posts  |
+      | [1]    |
+      | [1, 2] |
+
+  Scenario: Initialized with no value and an incorrect member size
+    When using a validation set like
+      """
+      object.has.posts
+
+      """
+    When the instance 'posts' attribute is '[]'
+    Then the validation set should fail
+
+  Scenario: Initialized with :no and the correct member size
+    When using a validation set like
+      """
+      object.has(:no).posts
+
+      """
+    When the instance 'posts' attribute is '[]'
+    Then the validation set should pass
+
+  Scenario: Initialized with :no and an incorrect member size
+    When using a validation set like
+      """
+      object.has(:no).posts
+
+      """
+    When the instance 'posts' attribute is '[1]'
+    Then the validation set should fail
+
+  Scenario Outline: Initialized with a range and the correct member size
+    When using a validation set like
+      """
+      object.has(2..3).posts
+
+      """
+    When the instance 'posts' attribute is '<posts>'
+    Then the validation set should pass
+
+    Examples:
+      | posts     |
+      | [1, 2]    |
+      | [1, 2, 3] |
+
+  Scenario Outline: Initialized with a range and an incorrect member size
+    When using a validation set like
+      """
+      object.has(2..3).posts
+
+      """
+    When the instance 'posts' attribute is '<posts>'
+    Then the validation set should fail
+
+    Examples:
+      | posts        |
+      | []           |
+      | [1]          |
+      | [1, 2, 3, 4] |

data/features/has_matcher_relativities.feature

@@ -0,0 +1,171 @@
+Feature: Has matcher relativities
+  In order to validate collections whose length may vary
+  I want to be able to validate that it has a minimum or maximum length
+
+  Background:
+    Given a class with a 'name' attribute
+
+  #
+  # 'exactly' is aliased as 'eql' and can also be omitted completely. See
+  # has_matcher_with_initialized_expectation feature for examples.
+  #
+
+  Scenario: Passing validation with exactly
+    When using a validation set like
+      """
+      object.name.has.exactly(5).characters
+
+      """
+    When the instance 'name' attribute is 'Dwigt'
+    Then the validation set should pass
+      And there should be no validation errors
+
+  Scenario: Failing validation with exactly
+    When using a validation set like
+      """
+      object.name.has.exactly(5).characters
+
+      """
+    When the instance 'name' attribute is ''
+    Then the validation set should fail
+      And the error on 'name' should be 'Name should have 5 characters'
+
+  #
+  # 'fewer_than' is aliased as 'lt' and 'less_than'
+  #
+
+  Scenario: Passing validation with lte
+    When using a validation set like
+      """
+      object.name.has.fewer_than(6).characters
+
+      """
+    When the instance 'name' attribute is 'Dwigt'
+    Then the validation set should pass
+      And there should be no validation errors
+
+  Scenario: Failing validation with lte
+    When using a validation set like
+      """
+      object.name.has.fewer_than(6).characters
+
+      """
+    When the instance 'name' attribute is 'abcdef'
+    Then the validation set should fail
+      And the error on 'name' should be 'Name should have at most 5 characters'
+
+  #
+  # 'at_most' is aliased as 'lte'
+  #
+
+  Scenario: Passing validation with lte
+    When using a validation set like
+      """
+      object.name.has.at_most(5).characters
+
+      """
+    When the instance 'name' attribute is 'Dwigt'
+    Then the validation set should pass
+      And there should be no validation errors
+
+  Scenario: Failing validation with lte
+    When using a validation set like
+      """
+      object.name.has.at_most(5).characters
+
+      """
+    When the instance 'name' attribute is 'abcdef'
+    Then the validation set should fail
+      And the error on 'name' should be 'Name should have at most 5 characters'
+
+  #
+  # 'at_least' is aliased as 'gte'
+  #
+
+  Scenario: Passing validation with gte
+    When using a validation set like
+      """
+      object.name.has.at_least(5).characters
+
+      """
+    When the instance 'name' attribute is 'Dwigt'
+    Then the validation set should pass
+      And there should be no validation errors
+
+  Scenario: Failing validation with gte
+    When using a validation set like
+      """
+      object.name.has.at_least(5).characters
+
+      """
+    When the instance 'name' attribute is ''
+    Then the validation set should fail
+      And the error on 'name' should be 'Name should have at least 5 characters'
+
+  #
+  # 'greater_than' is aliased as 'gt' and 'more_than'
+  #
+
+  Scenario: Passing validation with gte
+    When using a validation set like
+      """
+      object.name.has.greater_than(4).characters
+
+      """
+    When the instance 'name' attribute is 'Dwigt'
+    Then the validation set should pass
+      And there should be no validation errors
+
+  Scenario: Failing validation with gte
+    When using a validation set like
+      """
+      object.name.has.greater_than(4).characters
+
+      """
+    When the instance 'name' attribute is 'abcd'
+    Then the validation set should fail
+      And the error on 'name' should be 'Name should have at least 5 characters'
+
+  #
+  # between
+  #
+
+  Scenario: Passing validation with between and a range
+    When using a validation set like
+      """
+      object.name.has.between(2..5).characters
+
+      """
+    When the instance 'name' attribute is 'Dwigt'
+    Then the validation set should pass
+      And there should be no validation errors
+
+  Scenario: Failing validation with between two values and a range
+    When using a validation set like
+      """
+      object.name.has.between(2..5).characters
+
+      """
+    When the instance 'name' attribute is ''
+    Then the validation set should fail
+      And the error on 'name' should be 'Name should have between 2 and 5 characters'
+
+  Scenario: Passing validation with between and two values
+    When using a validation set like
+      """
+      object.name.has.between(2, 5).characters
+
+      """
+    When the instance 'name' attribute is 'Dwigt'
+    Then the validation set should pass
+      And there should be no validation errors
+
+  Scenario: Failing validation with between and two values
+    When using a validation set like
+      """
+      object.name.has.between(2, 5).characters
+
+      """
+    When the instance 'name' attribute is ''
+    Then the validation set should fail
+      And the error on 'name' should be 'Name should have between 2 and 5 characters'