Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

What are the advantages of creating your own classes in SilkTest?

What are the advantages of creating your own classes in SilkTest?

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:

  • Gives more control to the architecture maintenance effort.
  • Can handle any additional tasks that you may need before interacting with a particular object.
  • Can prove to be very useful for debugging purposes.
  • Can be customized to capture more detailed results.
  • Hides or encapsulates implementation details to end user.

In the testcase, HomePage.Welcome.GetText () will reference the GetText method in HtmlText2 specifically because "Welcome" is of the HtmlText2 class.

Old KB# 21798


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 19:24
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.