Squish

You can modify ControlsExt.qml to do this: https://doc.qt.io/squish/how-to-use-the-qml-extension-api.html#qml-extension-api

Modify the isIgnored function in the qml file.

@papers, please To code and test Squish Python scripts with PyCharm, first ensure Squish is installed and properly configured on your system. Add the Squish binary path to the environment variables so PyCharm can access Squish commands. In PyCharm, set up a new Python project and configure the interpreter to include Squish libraries. You can now write and test Squish scripts directly within PyCharm's editor.

Similar discussion was posted previously.
https://forum.qt.io/topic/150569/coding-squish-python-with-pycharm

Question first but if answer is no right now, could be a feature request ...

Hi,

AFAIR, 6.2 is too old to have a pre-built package for macOS ARM.

I am currently in contact with Squish's QA support, will post the solution here if/when we find it.

In case you want to access to file on remote system (where squishserver is running),
you should access them via functions offered by "remotesystem" object.
For more information regarding this object please refer to the following documentation.
https://doc.qt.io/squish/squish-api.html#remotesystem-object

As workaround to overcome native file dialog, please refer to the following Knowledge Base article.
https://kb.froglogic.com/squish/qt/howto/automating-native-file-dialogs/

Yes, import urllib.request is the correct one. But I used import urllib just to reproduce the fatal error while running the squish test. urllib is not the concern of this topic. I want to discuss the exit code of squishrunner with --retry 1 whenever there is a fatal error. I would expect the non-zero exit code but it returns 0.

Looking into this further, I think "import squishtest" is what we need.

We will look into compiling the "squishtest" module under QNX.

I got it running after inserting 2 times the omitted duration template parameter: long

Hi Barak,
I hope you were able to solve the issue by now. Just in case you are still struggling, I would need to know a bit more about your setup, the Squish package you are using, and the Qt libraries used by your application.

First of all, you need to ensure that you are using a Squish package that is compatible your your application:
https://doc.qt.io/squish/installing-from-binary-packages.html#choosing-the-correct-squish-package

If you think that you choose the right one but the problem still occurs, please share the squishserver logs generated after you start the application under test via Squish.

Hi Axel,

Thank you for your reply.

I checked my Qt packages, and libQt5Widgets is indeed installed, but the issue persists. I decided to reinstall my environment, including qtcreator-8.0.2 (Qt version 5.15.0 (gcc_64)) and squish-for-qt-8.0.0.

Now, Squish works within QtCreator, meaning that it still doesn't connect with other applications. The recording option can only capture and generate scripts of my actions inside QtCreator but not for the applications run by QtCreator. Thanks for your help.

Hi @clanhuth,

Thanks for the advice! I will look into this.

Cheers,
Bo

To test the effect, you need to add synchronization and verification. For example, if a button X appears (and is enabled and ready for interaction) after clicking button A, then, after letting the script click on button A, you could use waitForObject() to verify that button X exists and is "ready". However, this kind of object verification is implicit when you record a click on button A, then on button X, because Squish records waitForObject() (and the like) calls for mouse clicks automatically.