RuntimeError: startApplication() failed when using squish for testing Qt applications - qt

I am using Squish 4.2.2 for testing a GUI developed in Qt version 4.7 on linux. The AUT is built using statically linked Qt libraries. Since squish doesnot allow recording for statically linked Qt libraries, I am planning to manually create the test cases. However the squish test case fails with following error
Error Script Error Oct 31, 2012
Detail RuntimeError: startApplication() failed
The test case contains a single line to start the AUT. The server log shows only the following warning
AUT does not appear to be dynamically linked against Qt, hooking might fail.
Has anyone else faced a similar issue when testing Qt applications that are statically linked to Qt libraries? Kindly provide pointers for this issue.
Regards
adj

I have run into this error before and, one of the lessons learned was that the versions of Qt that your application is using
QtCore and QtGui
has to be compatible with the version of Qt squish was compiled with. If they are not, you get this error because squish cannot hook into the application.

You need to have the following correctly setup:
1. The version of Squish must be compatible with the version of Qt used to develop the app. Usually both versions must be the SAME to be compatible.
2. When setting up Squish, point it to the correct QtCore path.
3. Add the application in Edit -> Server Settings -> Manage AUT in the IDE.

Related

Qt error with reMarkable tablet app

I have a reMarkable tablet , which I mostly love except for the lack of linux support (surprising given it is a linux-based OS). However, I've managed to find a version of a linux application that is now unofficial. This github is actually a Qt docker app, but if you look in the code for the 'Dockerfile' you can find where to download the app, which is apparently still on the server even though there's not a link from the main web page. Anyway, I downloaded it and got it mostly working, figuring out a few dependencies based on same Dockerfile code. But, I can't seem to get file dialogs to work, which is the main reason for using the app.
The error I get is:
ERROR: No native FileDialog implementation available.
Qt Labs Platform requires Qt Widgets on this setup.
Add 'QT += widgets' to .pro and create QApplication in main().
I'm not a Qt developer, so I'm lost. I'd love to get this to work. Thanks.
In the .pro file of you project you should add this line QT += widgets
or just add widgets to the line with QT += ...
Qt can use native file dialogs on some platforms, and will fall back to its own implementation if none is available. But that requires that the application is built including the QtWidgets module, and using a QApplication.
If you don't have the source code of the app and a possiblity to rebuild it, there's no chance to fix this from a binary

Google NaCl with Qt on Windows

I have a project which is using Qt 4.7.4 version (also I can't rebuild it using qt4.8 or qt5 – there are a lot of errors appears, project is big and not mine so fixing issues would be even harder than erasing the whole code and write new code). So I need to make this project, well, working on NativeClient.
Is it even possible? I use Windows and Visual Studio, I was trying to google instructions about qt+nacl on Windows but just can’t find nothing.
Also which pepper version should I use if it depends on it?
Is your qt build supporting native client?
Please check out this
Windows
The Qt-Nacl is not support, for now, in Windows.
By the way, here is the github repository dedicated for it -> https://github.com/msorvig/qt5-qtbase-nacl
In the file nacl-readme it is written :
[...] Windows is not supported as a host platform.
Linux
If you want to compile in Linux, I have made a script that will compile Qt5.4 with NaCl with all the dependencies needed.
https://gist.github.com/theshadowx/438297ac465874a5e226
I also made a video that will show the different steps and a showCase at the end :
https://www.youtube.com/watch?v=q2pMv1Svtqw

Deploying Qt C++ Application from Visual Studio qwindows.dll error

I've been googling for a solution to this issue and although I've found many people sharing my problem none of their solutions work for me.
I wrote a C++ application using Qt framework using Visual Studio 2010. I built and ran the application in "Release" mode from Visual Studio without issue, but when I copy that exe from the Release folder to a new destination (pretend its a new PC) it fails to run providing this error:
---------------------------
TestApplication
---------------------------
This application failed to start because it could not find or load the Qt platform plugin "windows".
Available platform plugins are: windows.
Reinstalling the application may fix this problem.
Within the executable directory I have the following file structure:
./TestApplication.exe
./libGLESv2.dll
./Qt5Core.dll
./Qt5Gui.dll
./QtWidgets.dll
./platforms/qwindows.dll
./qt.conf
All dll files were taken from the 5.0.0 build of Qt in the Qtbase folder where the libraries reside.
The qt.conf file is:
[Paths]
Plugins=.
Without it, the launch error is the same except it says "minimal" and "offscreen" are available platforms as well.
For all other people experiencing this error it seemed to be solved by creating the platforms folder and putting in the qwindows.dll. But doing that myself doesn't change any behavior.
Is there something I've done wrong? Perhaps my method of generating the .exe in the first place is wrong?
If you are using libGLESv2.dll, then you must include libEGL.dll, too.
You can't see that in depends.exe, don't know how the Qt developers managed to hide this.
If your Qt is out of the box, then both Dlls are necessary even if you are not using OpenGL.
Also, if your Qt is out of the box, you need to include also the three ic*.dll, which contain information for Unicode handling.
You can see which DLLs are needed by looking at which ones are invoked when running Debug (F5) in Qt Creator.
=Carl
The release is likely missing a library/plugin or the library is in the wrong directory and or from the wrong directory.
Qt intended answer: Use windeployqt.
Qt comes with platform console applications that will add all dependencies (including ones like qwindows.dll and libEGL.dll) into the folder of your deployed executable. This is the intended way to deploy your application, so you do not miss any libraries (which is the main issue with all of these answers). The application for windows is called windeployqt. There is likely a deployment console app for each OS.

No qmlviewer installed

I've installed Qt SDK 5.0.0 beta 2 and Qt Creator 2.6.0. It detects the package but gives a warning that "No qmlviewer installed". I've looked for it and it is in the SDK bin folder. What can I do? I use ubuntu 12.04 and I've added the SDK binaries to the PATH. I can view the QML files through the terminal.
It is not a solution but maybe it will be helpful.
I can see this warning too, but I think it is not a big problem. I have started to move my existing Quick1 code to new Qt version and I have not seen Qt5 Kit in the drop down list. But when I have created new Quick2 application I found it. And everything seems to work without QMLviewer.
Btw, I found forum post about Qt5 and qmlveiwer. Guy says that it was very difficult to support viewer in the actual state because API of declarative modules are changing very quickly. So they have dropped qmlviewer from Qt5.

QML fails to load

I am a beginner to QML, just wanted to test the Hello WOrld program with it. It fails:
/home/saman# /home/saman/QtSDK/Simulator/Qt/gcc/bin/qmlviewer
Qml debugging is enabled. Only use this in a safe environment!
Cannot find any Simulator supporting Qt version 4.7.4.0.
Aborted
I need to know how to solve it.
It looks like you have not installed the Qt-SDK properly. Try to follow the installation instructions that came with the SDK or install it through your distributions package manager.
Try installing SDK (Qtcreator & Qt Kit) from https://download.qt.io/archive/qt/5.0/5.0.0/ (download required version depending on the platform you are working). This would inturn contain samples & demos which will work flawlessly.
All the best!

Resources