Forum Discussion

ChiefBrian's avatar
ChiefBrian
Contributor
2 months ago

15.72 Update Breaks all QT Desktop Testing

The 15.72 update breaks any all testing with a Desktop application using QT.

The update was supposed to include additional support for the current release of QT up to 6.7.

Instead it broke all QT support and even 6.7 doesn't work.

Even simple example apps from QT fail to work now.  

Posting as warning, if you test a desktop app I would not update.

Still waiting for a response from support, it has been 4 business days(as of 2/10) with no update from the support team on if they have reproduced issue or when it will be fixed.

Hopefully a fix will be released ASAP.

  • JDR2500's avatar
    JDR2500
    Frequent Contributor
    10 days ago

    I heard from support this morning.  They say the bug I reported with a 30-character group name limitation in the Execution Plan is fixed in 15.74.  However, they did not provide an ETA on 15.74.

    Hopefully the QT problem will also be fixed.

  • MW_Didata's avatar
    MW_Didata
    Regular Contributor
    17 days ago

    A new Update just released 15.73,

    Can you check if this is still an issue in 15.73?

  • sushant2023's avatar
    sushant2023
    New Member
    18 days ago

    Our existing automated suite for the desktop application is also not working after the upgrade from version 15.55 to 15.72,everything is broken now for TestComplete version of 15.72.60.

    • ChiefBrian's avatar
      ChiefBrian
      Contributor
      17 days ago

      Make sure you report this to smartbear.

      The most recent response I got from the support team indicated that it was by design and on purpose that they broke all desktop testing for QT applications without warning in a dot update.

      They have removed support for QT 6.2(LTS), and also skipped supported QT 6.5(LTS) and will only support the latest QT 6.8(LTS).    Since it was impossible to use TC with a QT version greater than 6.2 prior to this update, it means that all tests are broken now since the QT 6.2 applications will not be recognized by TestComplete anymore.

      It took 3.5 weeks for support to tell me this, so I am still not sure if they are just misinformed and this is actually a bug.  I am still awaiting a response back from them(average response time is about 3-5 days).

      I have so far been very disappointed with the support on this issue. And if this was really on purpose I would be very disappointed with how Smartbear treated us as customers.

      • JDR2500's avatar
        JDR2500
        Frequent Contributor
        17 days ago

        I find this "by design" business hard to believe.  You don't do that without clearly documenting it.  I'm sticking with it being a bug and support failing to recognize it as such.

        If you have an account manager at Smartbear you should contact them and complain.  15.72 was a major fail.  They should expedite releasing 15.73 with fixes for everything they broke.

  • ChiefBrian's avatar
    ChiefBrian
    Contributor
    23 days ago

    Update, it has now been 3 weeks since I reported this to support we have basically received what amounts to zero response from them.  They have sent responses, but they have not been informative or helpful.  

    We have even built and provided the simple QT example apps(that QT provides) so they have something simple to test with, since this is very easy to reproduce.  They still haven't not confirmed they have reproduced the actual issue. It is has been days since their last response to us.

    In the past support has been quite good, and at least responsive, but this experience has been very very poor especially given the gravity of the issue being the entire program just doesn't work any more.  We are extremely frustrated at this point. 

    Has anyone out there been able to get a response from Smartbear support on when the issues with the latest update will be resolved?

    • JDR2500's avatar
      JDR2500
      Frequent Contributor
      23 days ago

      They eventually reproduced the issue in 15.72 I reported with long group names in the Execution Plan.  This is the response I got late last week regarding what to expect:
      I went ahead and created an escalation with our operations team regarding this dialog prompt and group character limit. I'll update you here once I receive any new details from the development team. In the meantime, I would suggest downgrade TestComplete to the previous version to work around the issue.

  • ChiefBrian's avatar
    ChiefBrian
    Contributor
    2 months ago

    Have you gotten any real replies from the support team.   It has now been a week since we reported the issue and we have not received any real replies outside of the support tech saying they are "looking into it".    Have asked multiple times if they have been able to reproduce the issue, and they will not reply with anything other than boiler plate messages of we are looking into it.   Also we can only get one reply per day at 2:00am due to the support team be located in some other part of the world.

    Hopefully someone from the support team can read this and give us an update.

    • JDR2500's avatar
      JDR2500
      Frequent Contributor
      2 months ago

      Yes, I got a response from an actual person and started investigating the issue with them yesterday.  He and I have communicated back and forth a few times.

      I'm not sure why they responded to me but not you.  However, they did take forever to get back to me on a ticket I filed last summer.  It seems to be hit or miss.  

      The lag time caused by the overseas support is very unfortunate, and a disservice to US based customers.

  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3
    2 months ago

    There's a number of issues with the latest version, and I won't be surprised if other areas are broken too

    • nickp's avatar
      nickp
      29 days ago

      Yes, it broke our existing automated suite for Desktop application;  new version 15.72 fails to identify extended properties of Java Tables. 

    • JDR2500's avatar
      JDR2500
      Frequent Contributor
      2 months ago

      Our application is not QT, but 15.72 is also not working for us.  In our case MSVC object properties are not being found.  That's causing object recognition to fail for any Name Mapping items that use ClassName as one of the properties.  This was working fine in 15.69 and prior versions.

      I reported the issue to support.