1. Config: All your application configuration details and playback settings.
etc will go here
2. Library: All your libraries- application level, data access, exceptions, utilities will go here.
Please refer to Step 3
3. Resources: All your keys / strings that’s need to globally defined can be added here rather than hardcoding their values in code.
Example: The resource file key “SearchTimeOut” can be used to set playback settings as per your project needs without hardcoding it in your code.
4. Scripts: Your actual test are stored in these .cs files along with components like Test Initialize, Test Cleanup etc
5. Test Data: These will contain your .CSV or .XML test data files for your data-driven automation test
6. UIMaps: These will contain your test object repository along with any test methods or assertions (if any)
7. Main Class file: One class that acts as a single point interface to all the test methods and contains instantiations of the UI maps
etc will go here
2. Library: All your libraries- application level, data access, exceptions, utilities will go here.
Please refer to Step 3
3. Resources: All your keys / strings that’s need to globally defined can be added here rather than hardcoding their values in code.
Example: The resource file key “SearchTimeOut” can be used to set playback settings as per your project needs without hardcoding it in your code.
4. Scripts: Your actual test are stored in these .cs files along with components like Test Initialize, Test Cleanup etc
5. Test Data: These will contain your .CSV or .XML test data files for your data-driven automation test
6. UIMaps: These will contain your test object repository along with any test methods or assertions (if any)
7. Main Class file: One class that acts as a single point interface to all the test methods and contains instantiations of the UI maps
Комментариев нет:
Отправить комментарий