Forum Discussion

LOrban's avatar
LOrban
Occasional Contributor
11 years ago

Best practices for Scripting

Hi All, Being new with TC scripting technologies (however long time programmer), I’m trying to clarify the best practice to test web applications with JScripts. Consequently I woul...
  • Philip_Baird's avatar
    Philip_Baird
    11 years ago
    Hi László, using a combination of JScript Constructors and the Test Complete Page Object, it is possible to approximate the Selenium Page Object pattern.




    This provides the benefits of:



    1. Single point of contact to Page elements, if an element on a page changes, only a single point in the code needs changing to reflect the change. 


    2. Abstracting Page and Element interaction away from Test Scripts, Test Scripts need only know how to use a Page Object, the detail of addressing a Page element is hidden away making simplifying Test Scripts.


    3. Promotes re-usability



     


    For mine, this is the minimum standard to adhere to when writing automated Test Scripts for Browser applications. In fact, I use similar patterns for testing Windows forms applications.


     


    Regards,


    Phil Baird

Philip_Baird's avatar
Philip_Baird
Community Expert
11 years ago
Hi László, I see what you mean.

 


We basically use a JScript/Keyword Test hybrid in the following manner:


 


1. JScript to perform all the donkey work.


2. Keyword Tests to orchestrate execution of JScript functions in a try/catch/finally pattern that allows us to intercept failures and log results for automatic logging to a JIRA system post Test Execution. 


 


This also means that Testers that don't have strong development skills can still put together automated Tests.


 


Regards,


Phil Baird