I would also like some advice on improving usability within my test scripts. Unfortunately I took an early decision to make a new project for each functional area of my application in order to make maintenance of the name mapping easier but this severely limits re-usability between projects because TestComplete does not support referencing another projects NameMapping. I have worked around this by creating a common Project that does not rely on any name mapping items but does generic actions such as launching the application. However, I would still like to improve re-usability of shared functions within the project. Specifically - if I create reusable functions within keyword tests, how do I then differentiate these from actual keyword tests that call these functions (stringing these all together into an actual test)? I guess a naming convention could help.
nebsta you could create some naming convention yourself, eg. starting each general function with a special character eg "aaa" (or something like that),
also you can consider creating a feature request to Smartbear to start supporting referencing of other projects NameMapping files....
Thanks mgroen2 I will look at renaming the tests to get a standardized naming convention.
There is already a feature request to support referencing of a NameMapping from another project:
https://community.smartbear.com/t5/TestComplete-Feature-Requests/Support-references-to-NameMappings-of-other-projects/idi-p/116631 but is still currently classified as a new idea so could be some time off being implemented.
nebsta Thanks for the link to the feature request. I give it a +1 hopefully this will make a (small) difference :)
OK... not Keyword Driven Tests ala TestComplete... but, what about a Table Driven Framework where you would have some test developers working on maintaining the framework code but allow actual testers to construct test cases using only CSV files as the editing?
Check out..
https://bitbucket.org/tristaanogre/tabledrivenframework
