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

Marsha_R's avatar
Marsha_R
Moderator
11 years ago
I suppose it could depend on what you are testing but we have Keyword Tests with a few scripts mixed in and I have used TestComplete with straight scripting before and I don't see that there's much difference in keeping it updated as development goes along.  We change stuff all the time.  



I can think of some instances where search/replace might work better in scripts than it does in Keyword Tests, but otherwise maybe the difference is in the learning curve?  If you are already familiar with scripting then using Keyword Tests can seem a little clunky.