Forum Discussion

LOrban's avatar
LOrban
Occasional Contributor
10 years ago
Solved

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
    10 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

LOrban's avatar
LOrban
Occasional Contributor
10 years ago
Thanks Phil!



I set my head back into the proper top-down programming while “grinding” myself through the implementation of web-based testing and I realized what my real question would have been…



Due to TestComplete’s flexibility I see about 4 major ways of implementing automated testing:



  • Keyword testing:


    • Advantage:  quick to implement


    • Disadvantage:  difficult to maintain with development changes;




  • Keyword with Script testing (“hybrid” mode):


    • Advantage:  easy transition


    • Disadvantage:  even more tedious to keep updated both types during the development changes;




  • Script testing while relying on Stores Objects and NameMappings:


    • Advantage:  easy name referencing


    • Disadvantage:  in spite of nice UI-s updating options, the process is still not quick




  • “bare” Script testing through methods defined at:  (http://support.smartbear.com/viewarticle/62116/ ;   http://support.smartbear.com/viewarticle/56634/)


    • Advantage:  simply program scripting implementation


    • Disadvantage:  less documented?




By following the forum threads, I guess the last way of testing is used by most of the “deep-drilling” TC users…?



Note: during our web testing I had to go with the QuerySelector() and QuerySelectorAll() search methods with patterns stored in CSV files, for our web-pages are “heavily” relying on Dojo component that assigns on the fly different ID-s to most of the web-objects.



Cheers,

Lto