Forum Discussion
As per my understanding, this configuration can only be used if the application is in multi language .
Usually if the application is in English only then we can use Default Configuration
Please advise
Thanks
NG
- tristaanogre9 years agoEsteemed Contributor
Multi-language is one usage but is not the only usage.
In our case, we have two versions of our application that we need to run our tests against. Between those two versions, some of the property values are different. The objects and hierarchy are the same, but the property values are different. So, what we do is we use the configuration to "version" our NameMapping for the different application versions.
- nisgupta9 years agoValued Contributor
As mentioned that you are using 2 version of application and accordingly 2 version of Name mapping . But then what is the benefit ?
- tristaanogre9 years agoEsteemed Contributor
Nope... one NameMapping version, two configurations. So, if I want to run my tests against version one, I simply select (either manually or in code), the configuration for version one. If I want to run my tests against version two, the same. There aren't two separate files, just one file with two different configuration sets. That way I don't have to worry about keeping track of file versions, I just make sure I select the appropriate configuration.
Again, versioning is just an example. The point of configurations is that you may have two different environments (version, language, location, host, browser, etc) that require different property values for your mapped objects. Rather than having to create entirely separate mappings, you have one mapping where the values on the properties are just differentiated by configuration.
- Marsha_R9 years ago
Champion Level 3
The languages were just an example. You can separate the configurations any way you like, say versions of your software or locations of your offices
configurations
Version1
Version2
Version2.2
offices
Seattle
SanFrancisco
LosAngeles
whatever you need