ChiefBrian
Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: 15.72 Update Breaks all QT Desktop Testing
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.81Views0likes1CommentRe: 15.72 Update Breaks all QT Desktop Testing
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?98Views0likes1CommentRe: 15.72 Update Breaks all QT Desktop Testing
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.153Views0likes1Comment15.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.309Views1like14CommentsRe: dotNET.System_IO doesn't exist anymore?
Glad to hear you got it confirmed as a bug. I submitted a report almost a week ago. My tech only replied saying he would be on vacation for a week and I would have to wait till he gets back for a response. Hopefully a fix comes soon.35Views0likes0CommentsonLogError Event handler should handle Freeze Diagnostics Error
If an error is logged as a result of the Freeze Diagnostics this should be handled by the onLogError event handler so the user can add code to set how the test reacts to the freeze. Currently this is not handled(confirmed by smartbear support) which makes the Freeze Diagnostic tool almost useless since the user cannot program the test to react to the freeze. The test just ends, which basically no different than if the freeze diagnostic is off. This is very similar to the process crashed message also ignores the event handler. https://community.smartbear.com/idea/testxcompletefeaturerequests/onlogerror-event-handler-should-handle-process-crashed-message/233461 Really all errors should go through event handler or else it just become this guessing game of when it will and when it won't work...even if the issues are documented as they are with the crash error.