Forum Discussion

wmtan01's avatar
wmtan01
Contributor
5 years ago
Solved

Maximizing TestComplete to build efficient scripts

Hi everyone,   We're starting to increase the number of people handling TestComplete scripts in our company and I just wanted to read/know about how people develop their cases in TestComplete. I ca...
  • tristaanogre's avatar
    tristaanogre
    5 years ago

    Here's my take on that:

     

    Selenium, while good, you have to do EVERYTHING in code... I mean, EVERYTHING.  Object identification, building classes, wrapping things for a unit test to include in some testing tool, etc.  EVERYTHING.

     

    TestComplete:

    ObjectIdentifciation -> NameMapping

    Classes -> Code units/KWT

    Unit tests -> Test items, projects, etc

    Reports/Logs -> TestComplete logging

     

    A lot of the stuff you have to do manually in Selenium, TestComplete has built in.  

     

    Other advantage: Selenium is web only.  So, if you need to mix your tests between Desktop, API, Mobile, and Web, you need multiple tools.  TestComplete allows you to do ALL of them in one tool...or incorporate a few other tools into that one tool.  That Web Store that I mentioned above?  That was half of the pipeline of a ticket transaction.  There were reports, fulfillment, access control scanning, etc., done by other application platforms including desktop, kiosk, and mobile.  So, TestComplete allowed an all-in-one tool.

     

    Finally... Selenium is open source... which means that if you need support... well, you can hope you find the right guy in the right forum who knows what they're doing.  TestComplete has this space and their own dedicated customer service staff.  

     

    Again.. my opinion... others may vary but hopefully this helps in your decision processing.

wmtan01's avatar
wmtan01
Contributor

Thanks for the reply! 

 

Just out of curiousity if you are investing heavily on scripting, wouldn't it be better to actually use Selenium or a pure software testing tool? We are also at a crossroad where we are looking into other tools. I personally prefer TestComplete because it makes handling of test data much easier and the namemapping helps with the element locators. Another advantage would also be that it's friendly to some members of our team who are not comfortable with scripting. But I'm curious of what reasons other people have. :smileyhappy:

tristaanogre's avatar
tristaanogre
Esteemed Contributor
5 years ago

Here's my take on that:

 

Selenium, while good, you have to do EVERYTHING in code... I mean, EVERYTHING.  Object identification, building classes, wrapping things for a unit test to include in some testing tool, etc.  EVERYTHING.

 

TestComplete:

ObjectIdentifciation -> NameMapping

Classes -> Code units/KWT

Unit tests -> Test items, projects, etc

Reports/Logs -> TestComplete logging

 

A lot of the stuff you have to do manually in Selenium, TestComplete has built in.  

 

Other advantage: Selenium is web only.  So, if you need to mix your tests between Desktop, API, Mobile, and Web, you need multiple tools.  TestComplete allows you to do ALL of them in one tool...or incorporate a few other tools into that one tool.  That Web Store that I mentioned above?  That was half of the pipeline of a ticket transaction.  There were reports, fulfillment, access control scanning, etc., done by other application platforms including desktop, kiosk, and mobile.  So, TestComplete allowed an all-in-one tool.

 

Finally... Selenium is open source... which means that if you need support... well, you can hope you find the right guy in the right forum who knows what they're doing.  TestComplete has this space and their own dedicated customer service staff.  

 

Again.. my opinion... others may vary but hopefully this helps in your decision processing.

  • BenoitB's avatar
    BenoitB
    Community Hero
    5 years ago

    I agree with on most of points.

     

    I use scripting in TC since TC 6.5 ......

    Tried KWT but not convinced at all.

     

    Now i have a very complete framework allowing me to manage quite everything (even AS/400 mainframe). We were up to 10 persons using this framework approach (using Closure way of things) on my team in my previous company.

     

    But script need far more personal involvments than KWT.  In fine you are a pure developer BUT with real end-user mind. The best combination.

     

    About Selenium, most of its disavantadges were removed with Katalon Studio but TC scripting is still far better. For example the object search in TC is not limited to Xpath search.

     

    Could write a book on this subject but just not having the time for ..