hydra_attribute 0.3.2 → 0.4.0.rc1

data/features/query_methods/order.feature

@@ -1,99 +0,0 @@
-Feature: order conditions by hydra attributes
-  When order records by hydra attribute
-  Then correct table should be joined and order by value should be added
-
-  When correct table is already joined
-  Then only order condition should be added
-
-  When order by several attributes
-  Then order all of them by ascending
-
-  When reorder by attributes
-  Then old hydra attributes should be removed and new should be added
-
-  Background: create hydra attributes
-    Given create hydra attributes for "Product" with role "admin" as "hashes":
-      | name           | backend_type     | white_list     |
-      | [string:code]  | [string:integer] | [boolean:true] |
-      | [string:state] | [string:integer] | [boolean:true] |
-      | [string:title] | [string:string]  | [boolean:true] |
-
-  Scenario Outline: order by one field
-    Given create "Product" model with attributes as "hashes":
-      | name       | code        | state       |
-      | [string:c] | [integer:1] | [integer:1] |
-      | [string:b] | [integer:2] | [integer:2] |
-      | [string:a] | [integer:3] | [integer:3] |
-    When order "Product" records by "<attributes>"
-    Then "first" record should have "<first identifier>"
-    And "last" record should have "<last identifier>"
-
-    Scenarios: order conditions
-      | attributes | first identifier | last identifier  |
-      | state=asc  | code=[integer:1] | code=[integer:3] |
-      | state=desc | code=[integer:3] | code=[integer:1] |
-      | name=asc   | code=[integer:3] | code=[integer:1] |
-      | name=desc  | code=[integer:1] | code=[integer:3] |
-
-  Scenario Outline: order by several attributes
-    Given create "Product" model with attributes as "hashes":
-      | name       | code        | state       | title      |
-      | [string:c] | [integer:1] | [integer:1] | [string:b] |
-      | [string:b] | [integer:2] | [integer:2] | [string:a] |
-      | [string:a] | [integer:3] | [integer:3] | [string:c] |
-    When order "Product" records by "<attributes>"
-    Then "first" record should have "<first identifier>"
-    And "last" record should have "<last identifier>"
-
-    Scenarios: order conditions
-      | attributes  | first identifier | last identifier  |
-      | name state  | code=[integer:3] | code=[integer:1] |
-      | state title | code=[integer:1] | code=[integer:3] |
-      | title state | code=[integer:2] | code=[integer:3] |
-
-  Scenario Outline: order by filtered attribute
-    Given create "Product" model with attributes as "hashes":
-      | code        | state       | title      |
-      | [integer:1] | [integer:1] |            |
-      | [integer:2] |             | [nil:]     |
-      | [integer:3] | [integer:1] | [string:a] |
-    When filter "Product" records by "<filter attribute>"
-    And order records by "<order attributes>"
-    Then total records should be "<count>"
-    And "first" record should have "<first identifier>"
-    And "last" record should have "<last identifier>"
-
-    Scenarios: order conditions
-      | filter attribute  | order attributes | count | first identifier | last identifier  |
-      | state=[integer:1] | state code       | 2     | code=[integer:1] | code=[integer:3] |
-      | state=[nil:]      | state code       | 1     | code=[integer:2] | code=[integer:2] |
-      | title=[nil:]      | title code       | 2     | code=[integer:1] | code=[integer:2] |
-
-  Scenario Outline: reorder
-    Given create "Product" model with attributes as "hashes":
-      | code        | name       | title      |
-      | [integer:1] | [string:a] | [string:c] |
-      | [integer:2] | [string:b] | [string:b] |
-      | [integer:3] | [string:c] | [string:a] |
-    When order "Product" records by "<order>"
-    And reorder records by "<reorder>"
-    Then total records should be "<count>"
-    And "first" record should have "<first identifier>"
-    And "last" record should have "<last identifier>"
-
-    Scenarios: order conditions
-      | order | reorder    | count | first identifier | last identifier  |
-      | title | name title | 3     | code=[integer:1] | code=[integer:3] |
-      | name  | title name | 3     | code=[integer:3] | code=[integer:1] |
-
-  Scenario: reverse order
-    Given create "Product" model with attributes as "hashes":
-      | code        | title      |
-      | [integer:1] | [string:a] |
-      | [integer:2] | [string:b] |
-      | [integer:3] | [string:c] |
-    When order "Product" records by "title"
-    And reverse order records
-    Then total records should be "3"
-    And "first" record should have "code=[integer:3]"
-    And "last" record should have "code=[integer:1]"

data/features/query_methods/select.feature

@@ -1,50 +0,0 @@
-Feature: select concrete attributes
-  When select concrete attribute
-  Then model should response only to these attributes
-
-  Background: create hydra attributes
-    Given create hydra attributes for "Product" with role "admin" as "hashes":
-      | name              | backend_type      | white_list     |
-      | [string:code]     | [string:integer]  | [boolean:true] |
-      | [string:price]    | [string:float]    | [boolean:true] |
-      | [string:title]    | [string:string]   | [boolean:true] |
-      | [string:note]     | [string:text]     | [boolean:true] |
-      | [string:active]   | [string:boolean]  | [boolean:true] |
-      | [string:schedule] | [string:datetime] | [boolean:true] |
-    And create "Product" model with attributes as "hashes":
-      | name       | code        | price     | title      | note       | active          | schedule              |
-      | [string:a] | [integer:1] | [float:4] | [string:q] | [string:z] | [boolean:true]  | [datetime:2012-06-01] |
-      | [string:b] | [integer:2] | [float:5] | [string:w] | [string:x] | [boolean:false] | [datetime:2012-06-02] |
-      | [string:c] | [integer:3] | [float:6] |            | [string:c] | [boolean:true]  | [datetime:2012-06-03] |
-      | [string:d] | [nil:]      | [float:7] |            | [string:v] | [boolean:false] | [datetime:2012-06-04] |
-
-  Scenario Outline: select concrete attributes
-    When "Product" select only the following columns "<selected columns>"
-    Then records should have only the following "<expected columns>" names
-    And records should raise "ActiveModel::MissingAttributeError" when call the following "<methods>"
-    And total records should be "4"
-
-    Scenarios: select attributes
-      | selected columns  | expected columns     | methods                               |
-      | name              | name                 | code price title note active schedule |
-      | name code         | id name code         | price title note active schedule      |
-      | name code price   | id name code price   | title note active schedule            |
-      | code price title  | id code price title  | name note active schedule             |
-      | title note active | id title note active | name code price schedule              |
-      | schedule          | id schedule          | name code price title note active     |
-      | id schedule       | id schedule          | name code price title note active     |
-
-  Scenario Outline: filter collection and select concrete attributes
-    When "Product" select only the following columns "<selected columns>"
-    And filter records by "<filter attributes>"
-    Then records should have only the following "<expected columns>" names
-    And records should raise "ActiveModel::MissingAttributeError" when call the following "<methods>"
-    And total records should be "<total>"
-
-    Scenarios: filter and select attributes
-      | selected columns | expected columns | filter attributes | methods                               | total |
-      | name code        | id name code     | name=[string:a]   | price title note active schedule      | 1     |
-      | code             | id code          | code=[integer:1]  | name price title note active schedule | 1     |
-      | name code        | id name code     | code=[integer:1]  | price title note active schedule      | 1     |
-      | code title       | id code title    | title=[nil:]      | name price note active schedule       | 2     |
-      | code note        | id code note     | title=[nil:]      | name price title active schedule      | 2     |

data/features/query_methods/where.feature

@@ -1,70 +0,0 @@
-Feature: hydra attribute where conditions
-  When filter by hydra attribute and this value is not nil
-  Then records with this attribute should be selected
-
-  When filter by hydra attribute and this value is nil
-  Then records with nil and blank value should be selected
-
-  Background: create hydra attributes
-    Given create hydra attributes for "Product" with role "admin" as "hashes":
-      | name             | backend_type     | white_list     |
-      | [string:code]    | [string:string]  | [boolean:true] |
-      | [string:summary] | [string:string]  | [boolean:true] |
-      | [string:title]   | [string:string]  | [boolean:true] |
-      | [string:price]   | [string:float]   | [boolean:true] |
-      | [string:active]  | [string:boolean] | [boolean:true] |
-      | [string:state]   | [string:integer] | [boolean:true] |
-
-  Scenario: filter by one hydra attribute
-    Given create "Product" model with attributes as "hashes":
-      | code       | price        |
-      | [string:1] | [float:2.75] |
-      | [string:2] | [float:2.75] |
-      | [string:3] | [float:2.76] |
-      | [string:4] | [nil:]       |
-    When filter "Product" by:
-      | field | value         |
-      | price | [string:2.75] |
-    Then total records should be "2"
-    And records should have the following attributes:
-      | field | value      |
-      | code  | [string:1] |
-      | code  | [string:2] |
-
-  Scenario: filter by one hydra attribute with nil value
-    Given create "Product" model with attributes as "hashes":
-      | code       | price     |
-      | [string:1] | [nil:]    |
-      | [string:2] | [float:0] |
-      | [string:3] |           |
-    When filter "Product" by:
-      | field | value  |
-      | price | [nil:] |
-    Then total records should be "2"
-    And records should have the following attributes:
-      | field | value      |
-      | code  | [string:1] |
-      | code  | [string:3] |
-
-  Scenario: filter by several fields including both the hydra and general attributes
-    Given create "Product" model with attributes as "hashes":
-      | name         | code       | title          | price        | active          | state  | summary |
-      | [string:toy] | [string:1] | [string:story] | [float:2.40] | [boolean:true]  |        |         |
-      | [string:toy] | [string:2] | [string:story] | [float:2.45] | [boolean:true]  |        | [nil:]  |
-      | [string:toy] | [string:3] | [string:story] | [float:2.45] | [boolean:true]  | [nil:] | [nil:]  |
-      | [string:toy] | [string:4] |                | [float:2.45] | [boolean:false] | [nil:] | [nil:]  |
-      |              | [string:5] |                | [float:2.45] | [boolean:true]  | [nil:] | [nil:]  |
-      | [string:toy] | [string:6] |                | [float:2.46] | [boolean:true]  | [nil:] | [nil:]  |
-    When filter "Product" by:
-      | field   | value          |
-      | name    | [string:toy]   |
-      | title   | [string:story] |
-      | summary | [nil:]         |
-      | price   | [string:2.45]  |
-      | active  | [boolean:true] |
-      | state   | [nil:]         |
-    Then total records should be "2"
-    And records should have the following attributes:
-      | field | value      |
-      | code  | [string:2] |
-      | code  | [string:3] |

data/features/support/schema.rb

@@ -1,79 +0,0 @@
-ActiveRecord::Schema.define do
-  create_table "products", :force => true do |t|
-    t.string  "name"
-    t.datetime "created_at",                :null => false
-    t.datetime "updated_at",                :null => false
-  end
-
-  create_table "hydra_attributes", :force => true do |t|
-    t.string   "entity_type",   :limit => 32, :null => false
-    t.string   "name",          :limit => 32, :null => false
-    t.string   "backend_type",  :limit => 16, :null => false
-    t.string   "default_value"
-    t.boolean  "white_list",                  :null => false, :default => false
-    t.datetime "created_at",                  :null => false
-    t.datetime "updated_at",                  :null => false
-  end
-
-  add_index "hydra_attributes", ["entity_type", "name"], :name => "hydra_attributes_index", :unique => true
-
-  create_table "hydra_boolean_products", :force => true do |t|
-    t.integer  "entity_id",          :null => false
-    t.integer  "hydra_attribute_id", :null => false
-    t.boolean  "value"
-    t.datetime "created_at",         :null => false
-    t.datetime "updated_at",         :null => false
-  end
-
-  add_index "hydra_boolean_products", ["entity_id", "hydra_attribute_id"], :name => "hydra_boolean_products_index", :unique => true
-
-  create_table "hydra_datetime_products", :force => true do |t|
-    t.integer  "entity_id",          :null => false
-    t.integer  "hydra_attribute_id", :null => false
-    t.datetime "value"
-    t.datetime "created_at",         :null => false
-    t.datetime "updated_at",         :null => false
-  end
-
-  add_index "hydra_datetime_products", ["entity_id", "hydra_attribute_id"], :name => "hydra_datetime_products_index", :unique => true
-
-  create_table "hydra_float_products", :force => true do |t|
-    t.integer  "entity_id",          :null => false
-    t.integer  "hydra_attribute_id", :null => false
-    t.float    "value"
-    t.datetime "created_at",         :null => false
-    t.datetime "updated_at",         :null => false
-  end
-
-  add_index "hydra_float_products", ["entity_id", "hydra_attribute_id"], :name => "hydra_float_products_index", :unique => true
-
-  create_table "hydra_integer_products", :force => true do |t|
-    t.integer  "entity_id",          :null => false
-    t.integer  "hydra_attribute_id", :null => false
-    t.integer  "value"
-    t.datetime "created_at",         :null => false
-    t.datetime "updated_at",         :null => false
-  end
-
-  add_index "hydra_integer_products", ["entity_id", "hydra_attribute_id"], :name => "hydra_integer_products_index", :unique => true
-
-  create_table "hydra_string_products", :force => true do |t|
-    t.integer  "entity_id",          :null => false
-    t.integer  "hydra_attribute_id", :null => false
-    t.string   "value"
-    t.datetime "created_at",         :null => false
-    t.datetime "updated_at",         :null => false
-  end
-
-  add_index "hydra_string_products", ["entity_id", "hydra_attribute_id"], :name => "hydra_string_products_index", :unique => true
-
-  create_table "hydra_text_products", :force => true do |t|
-    t.integer  "entity_id",          :null => false
-    t.integer  "hydra_attribute_id", :null => false
-    t.text     "value"
-    t.datetime "created_at",         :null => false
-    t.datetime "updated_at",         :null => false
-  end
-
-  add_index "hydra_text_products", ["entity_id", "hydra_attribute_id"], :name => "hydra_text_products_index", :unique => true
-end

data/features/update.feature

@@ -1,114 +0,0 @@
-Feature: update hydra attributes
-  When update attribute
-  Then entity should be touched
-
-  Background: create hydra attributes
-    Given create hydra attributes for "Product" with role "admin" as "hashes":
-      | name           | backend_type     | default_value | white_list     |
-      | [string:code]  | [string:string]  | [string:###]  | [boolean:true] |
-      | [string:title] | [string:string]  |               | [boolean:true] |
-      | [string:total] | [string:integer] | [integer:1]   | [boolean:true] |
-    And create "Product" model
-
-  Scenario Outline: update attributes
-    Given select last "Product" record
-    When  assign attributes as "rows_hash":
-      | code  | <set code>  |
-      | title | <set title> |
-      | total | <set total> |
-    And save record
-    Then last created "Product" should have the following attributes:
-      | code  | <code>  |
-      | title | <title> |
-      | total | <total> |
-
-    Scenarios: attributes
-      | set code   | set title  | set total   | code         | title      | total       |
-      | [string:a] | [string:b] | [integer:2] | [string:a]   | [string:b] | [integer:2] |
-      | [string:]  | [string:]  | [nil:]      | [string:]    | [string:]  | [nil:]      |
-      |            |            | [string:3]  | [string:###] | [nil:]     | [integer:3] |
-
-  # Is a better solution to call several scenarios but don't call hooks and backgrounds before?
-  Scenario: update the same model several times
-    Given select first "Product" record
-    And save record
-    Then last created "Product" should have the following attributes:
-      | code  | [string:###] |
-      | title | [nil:]       |
-      | total | [integer:1]  |
-
-    When assign attributes as "rows_hash":
-      | title | [string:] |
-      | total | [nil:]    |
-    And save record
-    Then last created "Product" should have the following attributes:
-      | code  | [string:###] |
-      | title | [string:]    |
-      | total | [nil:]       |
-
-    When assign attributes as "rows_hash":
-      | code  | [string:a] |
-      | total | [string:2] |
-    And save record
-    Then last created "Product" should have the following attributes:
-      | code  | [string:a]  |
-      | title | [string:]   |
-      | total | [integer:2] |
-
-    When assign attributes as "rows_hash":
-      | title | [string:b] |
-    And save record
-    Then last created "Product" should have the following attributes:
-      | code  | [string:a]  |
-      | title | [string:b]  |
-      | total | [integer:2] |
-
-  Scenario: touch entity when attribute is updated
-    Given select last "Product" record
-    And keep "updated_at" attribute
-    And save record
-    Then attribute "updated_at" should be the same
-
-    Given select last "Product" record
-    And keep "updated_at" attribute
-    When assign attributes as "rows_hash":
-      | code  | [string:###] |
-      | total | [integer:1]  |
-    And save record
-    Then attribute "updated_at" should be the same
-
-    Given select last "Product" record
-    And keep "updated_at" attribute
-    When assign attributes as "rows_hash":
-      | code | [nil:] |
-    And save record
-    Then attribute "updated_at" should not be the same
-
-    Given select last "Product" record
-    And keep "updated_at" attribute
-    When assign attributes as "rows_hash":
-      | code | [nil:] |
-    And save record
-    Then attribute "updated_at" should be the same
-
-    Given select last "Product" record
-    And keep "updated_at" attribute
-    When assign attributes as "rows_hash":
-      | total | [nil:] |
-    And save record
-    Then attribute "updated_at" should not be the same
-
-    Given select last "Product" record
-    And keep "updated_at" attribute
-    When assign attributes as "rows_hash":
-      | code | [string:] |
-    And save record
-    Then attribute "updated_at" should not be the same
-
-    Given select last "Product" record
-    And keep "updated_at" attribute
-    When assign attributes as "rows_hash":
-      | title | [string:]   |
-      | total | [integer:0] |
-    And save record
-    Then attribute "updated_at" should not be the same