Forum Discussion

santi's avatar
santi
Contributor
6 years ago

Angular Material 8 not recognized by Test Complete

My application uses angular with material, It's not possible by test complete to identify material objects details from DOM. Any idea when the possible support expected if at all.
  • JuliaBernikova's avatar
    JuliaBernikova
    5 years ago

    Hi santi,

     

    The fastest way to resolve the issue is to reach out to our support team by submitting a case here - we will schedule a call to collect more info and find the cause of the recognition issues as soon as possible.

     

    AlexKaras, thank you for your assistance in this thread!

     

tristaanogre's avatar
tristaanogre
Esteemed Contributor
5 years ago

Most of the folks who frequent here are users just like you so we don't necessarily have that sort of inside track.

 

TanyaYatskovska  and sonya_m might be able to do some leg work.

HOWEVER...  I'm not sure why you're saying it can't see Angular Material controls.  From the documentation:


TestComplete can work with any web control via the control’s graphical user interface displayed in a web browser, no matter how the control is implemented on the server side. You can test web applications that use controls implemented by using various technologies and frameworks, including Angular frameworks and component libraries (like AngularUI, Angular Material, and etc.).

This can be found at https://support.smartbear.com/testcomplete/docs/general-info/supported-technologies/controls/angularui.html

 

So... it seems that angular material is supported... which tells me something else is wrong with your set up.  Double check to make sure that the plug-in is turned on (File -> Install Extensions)

  • sonya_m's avatar
    sonya_m
    SmartBear Alumni (Retired)
    5 years ago

    As far as I see, the topic is quite old. Let us know santi if this is still an issue!

    • santi's avatar
      santi
      Contributor
      5 years ago

      Thanks both for reply, and apology for responding late.

       

      We use Angular+Angular material for our application. There are many custom classes defined by development team, which generates it's own html structure. With change of custom class, other HTML (under material) will get changed.

      Test Complete (14.10,14.30) not identifying those custom classes, for which we are facing lot of issues and even may move out from the tool, as this is a major chunk of our automation.

      Yesterday we had meeting with top management and they have given us few days to find out (work around). 

       

      Does testcomplete provide any plug-in to support this ?

       

      common, desktop, mobile and web are the extensions we are using.

       

      Thanks for your time and kind reply.

      • AlexKaras's avatar
        AlexKaras
        Champion Level 3
        5 years ago

        Hi,

         

        > generates it's own html structure.

        Well... I assume that you are testing web application (web pages).

        I also assume that you are dealing with plain html markup (without any ActiveX components, widgets, etc.). Is that correct?

        If the above is correct, then TestComplete should be able to control those web pages.

        I do not remember to work with web pages created with Angular Material, but the regular Angular (as well as React) is well known in the automation world for its extremely poor symantic markup of the page which results in extremely difficult and expensive automation. Regardless of the tool been used.

         

        > Test Complete (14.10,14.30) not identifying those custom classes

        Could you clarify this? What was your exact expectation? Can you provide an example of the page markup with your comments as for what was not identified?

         

        > they have given us few days to find out (work around).

        Again, if my guess that your problem is with the absent page markup (web elements do not have unique and stable identifiers), then you will not get anything by replacing the tool. If the above is your case, you have only two options possible:

        a) Talk to Development and convince them to provide stable and unique identifiers for each and every web element that your test code needs to interact with;

        b) Spend time and efforts to figure out and implement in code some approach to reliably identify required web elements. Depending on your application, this well may be some intelligent search for parent and child elements, image search, search by text, etc.