Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We are working on automation various different web/client applications, using several different frameworks (WatiN, Ranorex for example).
My question is — what are the for/against for storing the actual object identification (the properties used to identify it at runtime) in the code (using attributes or whatever other mechanism), or extracting it to an external configuration file that will be read by the code executing.
Storing the object identification mechanism in code would
but at the same time would
Storing the object identification in configuration or a test data file would lead to an additional step that will retrieve the object identifiers from the file.
~Ashish Narmen