IMPORTANT NOTICE: As of 21 February, anything posted in this community WILL NOT BE MIGRATED to our new community site. We have pulled all user information and data from this site and are now in an approximately week long process of importing users, roles, and data to our new site. We are leaving this site open and active so you can post and hopefully get a response until the migration is complete. Once complete, the URL that currently takes you to this site will take you to our new site so your bookmarks will work as always. Please read the information on a New Login Process
One approach to solidifying a test architecture is to create your own classes (derived from standard SilkTest classes) and override/modify/add additional steps for each derived method contained within the derived class.
The benefits to this approach are great, but in order to succeed an investment must be made in order to create the class wrappers and secure the stability of the architecture. However, once complete, only the methods introduced by the class wrapping are published to the script writing team. Some, but not all, of the benefits to using this technique are:
In the testcase, HomePage.Welcome.GetText () will reference the GetText method in HtmlText2 specifically because "Welcome" is of the HtmlText2 class.