Here are some best practices to perform follow when you are working on the Test cases screen.
- In case sample Deactivate the projects that are created and are not used for any development. De-activate such projects to avoid any performance issues for users, while not in use anymore. This will reduce the performance issues facing when logging on to Qualitia Automation Studio.
- Define nomenclature (naming convention) before starting any development. For example:
- How user should name the objects to identify similar objects with different properties on different pages.
- Give comprehensive names or ids to the test cases making it easily understandable for other users.
- Create tasks if same set of steps is being used multiple times without any change. This would be very helpful as same task can be used in multiple situations and the user should be able to judge the task flow by the name of the task.
- While identifying objects with object spy, it is always better to keep the object spy IE window open. This comes in handy when the user is developing the test case and comes across object that is not added to the repository. Instead of switching tabs and adding objects manually, user can use the existing open instance of object spy and add objects instantly.
- Try dividing the complete test case in tasks as this would increase re-usability / modularity and also reduce development time of subsequent test cases.
- With multiple user scenario always use centralized repository (SVN) however, avoid manual check-in / check-out of any XML files.
- Always implement error handling flags on important and critical tasks under test case and apply the same concept for test suites as well.
- Qualitia supports multiple ways for execution of testcases. Try and implement any of the method instead of doing online executions.
- Define ‘ResultPath’ as shared path so that all users connecting to Qualitia can access all execution reports.