Forum Discussion

mgy333's avatar
mgy333
Contributor
14 years ago

Tag Model and Cross-Browser Testing feature in TestComplete 9

I have a lot of test scripts that tests webpages.  I use Tag model.  I like Tag model because it keeps the line of code relatively short compared to Tree model.



One of the nice new feature in TestComplete 9 is its cross browser testing capability.  As I was looking that, I noticed that Tree model is the default.  It gives warning if I try to use Tag model and use the new cross browser capability (by not checking "Use legacy web testing features" checkbox in option).  While it gives warning, I found that it still works under cross browing.



Does this mean Tag model is being phased out? 



My hope is to be able to keep using Tag model with cross browing capability because it would help us to be able to test for both IE and Firefox without additional code as we had before. 



Changing the entire code to use Tree model from Tag model would take very long time.

5 Replies

  • TanyaYatskovska's avatar
    TanyaYatskovska
    Icon for Alumni rankAlumni
    14 years ago

    Hi Motoo,


     


    The cross-browser feature works only for the Tree model. Other web tree models may assign different names under different browsers, and thus, the recorded test could be browser-dependent. As a result, we cannot rely on them.


     

  • mgy333's avatar
    mgy333
    Contributor
    14 years ago
    Then the other question: will the tag model be supported in future, or is it planned on being dropped?
  • TanyaYatskovska's avatar
    TanyaYatskovska
    Icon for Alumni rankAlumni
    14 years ago

    Hi Motoo,


     


    Currently, we aren't planning to implement this. However, we have a corresponding suggestion in our DB, and your request has increased its rating. Thanks!


     

  • mgy333's avatar
    mgy333
    Contributor
    14 years ago
    Thanks for the reply.



    My finding was that the cross browser capability worked well under tag model.  At least in  a short time I used it, I didn't see any issue. 



    It was just that it was putting warnings on log, which isn't ideal for a production environment.