This shows that all three mapping algorithms put out the same results when an Application Configuration Module tells them to.
This test also uses the fixture mapping facility - notice that the fixture names are more or less understandable, rather than being file system paths.
The first thing is to verify that the configuration is set up properly. Note that this test will not run correctly at the same time as Label Mapping if the runner tries to run the entire directory at one time. The configurations are incompatible.
check configuration | ||
Environment | Batch | |
Options | appConfigurationModule | fit.AccTestFixtures.ApplicationConfiguration1 |
Now do the same check as in the Label Mapping test, but use the values for Extended Camel in all three columns. Notice that this is using the same fixture as Label Mapping.
map label display | ||||
label | camel | graceful names | extended camel | notes |
hi there! | hiThereBang | hiThereBang | hiThereBang | "Bang" is a developer term. |
123.45 | one23Dot45 | one23Dot45 | one23Dot45 | |
pass | pass_ | pass_ | pass_ | "pass" is a Python reserved word |
try_this | try_this | try_this | try_this | Python regards _ as an alphabetic char, not a special character |
Leading caps | LeadingCaps | LeadingCaps | LeadingCaps | |
One2buckle My shoe | One2buckleMyShoe | One2buckleMyShoe | One2buckleMyShoe |