Test properties desired

[GoogleCodeExporter]

Often when configuring properties, we want a different value to be used when 
testing versus production. Today, the only thing we can do is create a test 
version of the property set, change the values to test values, run our tests, 
and when done, remember to delete this test version rather than accidentally 
promote to production.

Would like a feature like was done for the PAYPAL APIs so we can define both 
production and test values in the same property set.  So when in test mode, it 
will still look for a test version of a property set first, but if found or 
not, it will first see if the 'propertyName_TEST' exists and use that value if 
found before it looks for just 'propertyName'.

TEST and TEST LIKE PRODUCTION modes resolve to propertyName_TEST, then 
propertyName if not found.
PRODUCTION mode just look for propertyName.

The standard modes should be used to resolve property sets as before, so TEST 
mode looks for test propertysets first, and if none, uses the production 
version, while TEST LIKE PRODUCTION and PRODUCTION will only look for 
production property sets.

Original issue reported on code.google.com by yoz...@gmail.com on 29 Jul 2014 at 9:52

[GoogleCodeExporter]

This allows a property set to be created that has both production values 
(normal) and special test-only values.  The normal resolution of propertysets 
takes place for Production, Test Like Production and Test modes.  But if you 
define the same property name with an _TEST suffix and you are in Test Like 
Production or Test modes, it will return that property instead.  This is useful 
for property values that include more sensitive information that should not be 
used for tests (such as SSN/EIN, email addresses, passwords) and is used by the 
PayPal plugin so when testing you go against the PayPal test site rather than a 
real credit card charge.

Added in release 14.8.23.

Original comment by yoz...@gmail.com on 31 Jul 2014 at 12:09

• Changed state: Fixed