features/service.feature in ruby_odata-0.1.6 vs features/service.feature in ruby_odata-0.2.0.beta1

@@ -9,42 +9,42 @@
   And blueprints exist for the service
 
 Scenario: Service should respond to valid collections
   Then I should be able to call "Categories" on the service
 
-Scenario: Service should not respond to an invalid collection
-  Then I should not be able to call "X" on the service
-
-Scenario: Service should respond to accessing a single entity by ID
-  Then I should be able to call "Categories" on the service with args: "1"
-
-Scenario: Access an entity by ID should return the entity type
-  Given I call "AddToCategories" on the service with a new "Category" object with Name: "Test Category"
-  And I save changes
-  And I call "Categories" on the service with args: "1"
-  When I run the query
-  Then the first result should be of type "Category"
-
-Scenario: Entity should have the correct accessors
-  Given I call "AddToCategories" on the service with a new "Category" object with Name: "Test Category"
-  And I save changes
-  And I call "Categories" on the service with args: "1"
-  When I run the query
-  Then the first result should have a method: "Id"
-  And the first result should have a method: "Name"
-
-Scenario: Entity should fill values
-  Given I call "AddToCategories" on the service with a new "Category" object with Name: "Test Category"
-  And I save changes
-  And I call "Categories" on the service with args: "1"
-  When I run the query
-  Then the method "Id" on the first result should equal: "1"
-  And the method "Name" on the first result should equal: "Test Category"
-
-Scenario: Navigation Properties should be included in results
-  Given I call "AddToProducts" on the service with a new "Product" object
-  And I save changes
-  And I call "Products" on the service with args: "1"
-  When I run the query
-  Then the first result should have a method: "Category"
-  And the method "Category" on the first result should be nil
-
+# Scenario: Service should not respond to an invalid collection
+#   Then I should not be able to call "X" on the service
+# 
+# Scenario: Service should respond to accessing a single entity by ID
+#   Then I should be able to call "Categories" on the service with args: "1"
+# 
+# Scenario: Access an entity by ID should return the entity type
+#   Given I call "AddToCategories" on the service with a new "Category" object with Name: "Test Category"
+#   And I save changes
+#   And I call "Categories" on the service with args: "1"
+#   When I run the query
+#   Then the first result should be of type "Category"
+# 
+# Scenario: Entity should have the correct accessors
+#   Given I call "AddToCategories" on the service with a new "Category" object with Name: "Test Category"
+#   And I save changes
+#   And I call "Categories" on the service with args: "1"
+#   When I run the query
+#   Then the first result should have a method: "Id"
+#   And the first result should have a method: "Name"
+# 
+# Scenario: Entity should fill values
+#   Given I call "AddToCategories" on the service with a new "Category" object with Name: "Test Category"
+#   And I save changes
+#   And I call "Categories" on the service with args: "1"
+#   When I run the query
+#   Then the method "Id" on the first result should equal: "1"
+#   And the method "Name" on the first result should equal: "Test Category"
+# 
+# Scenario: Navigation Properties should be included in results
+#   Given I call "AddToProducts" on the service with a new "Product" object
+#   And I save changes
+#   And I call "Products" on the service with args: "1"
+#   When I run the query
+#   Then the first result should have a method: "Category"
+#   And the method "Category" on the first result should be nil
+#