Skip to content
Browse files

Fix missing closing tag on lazy-encoders.feature

It didn't break anything, but definitely doesn't look good.
  • Loading branch information...
1 parent 4678ba3 commit 3b5b26510f4fdada36f3c110113313d98affb287 @antifuchs committed Sep 9, 2012
Showing with 7 additions and 7 deletions.
  1. +7 −7 features/lazy_encoders.feature
View
14 features/lazy_encoders.feature
@@ -1,15 +1,15 @@
Feature: Lazy XML-RPC encoders
- As a client of a shoddy xml-rpc encoder,
- I want to be able to read their requests and responses correctly,
+ As a client of a shoddy xml-rpc encoder,
+ I want to be able to read their requests and responses correctly,
so that I can communicate with them.
Scenario: Implicit <string> types in <values>
Given the following method response:
"""
-<methodResponse><params><param><value>987lkjasd</value></param></params>
+<methodResponse><params><param><value>987lkjasd</value></param></params></methodResponse>
"""
When I decode the method response
Then the first value should be "987lkjasd"
@@ -21,10 +21,10 @@ Scenario: Implicit <string> types in <values> starting with whitespace
"""
<methodResponse><params><param><value>
987lkjasd
-</value></param></params>
+</value></param></params></methodResponse>
"""
When I decode the method response
- Then the first value should be:
+ Then the first value should be:
"""
987lkjasd
@@ -36,7 +36,7 @@ Scenario: Implicit <string> type starting with an XML entity
Given the following method response:
"""
-<methodResponse><params><param><value>&#32;987lkjasd</value></param></params>
+<methodResponse><params><param><value>&#32;987lkjasd</value></param></params></methodResponse>
"""
When I decode the method response
Then the first value should be " 987lkjasd"
@@ -48,7 +48,7 @@ Scenario: Indented, explicit type tags
"""
<methodResponse><params><param><value>
<string>987lkjasd</string>
-</value></param></params>
+</value></param></params></methodResponse>
"""
When I decode the method response
Then the first value should be "987lkjasd"

0 comments on commit 3b5b265

Please sign in to comment.
Something went wrong with that request. Please try again.