Squish

@jagadish Thank you

Hi @MRosiek

best way to see your remote screen is using the "Remote Control" in Squish IDE. from where you can use all other features of squish like the record video etc..

In your case its simple just open the VNC display on which ever your already using the TightVNC over 5900 port and run your test case,
You will see the application being launched by Squish and tested by Squish on this display.

I have used this in past and it works fine, this should solve your situation.
Let me know if this helps.

You can always raise support tickets directly from SquishIDE
https://doc.qt.io/squish/collect-information-for-squish-support-dialog.html

@Pritha-Suresh you can modify the path where the video is getting saved by passing the path to the "test.startVideoCapture(/path)"
to do animation testing you will need external tools like opencv or someting similar.
It will be easier to test any internal property corresponding to the animation rather than attempting to test the filling animation.

Hi there!
How about using text.vpWithObject? You should be able to pass a realname from your custom global object map as the second parameter.

Hi Mike,
I guess you are defining this function in a python module other than test.py. In general you have at least to ways to include such module in your test:

source it - https://doc.qt.io/squish/source-function.html#source-function use native python imports

The first approach lets you use your function as it is. However, in most of the cases I recommend using native python import, even though it may require some extra work from you. Your custom Python modules won't have any knowledge of the Squish API until you import the required modules—like the test module you mentioned.

import test def addMessageToLog(self, message): test.log(message)

You can learn more about it in the https://qatools.knowledgebase.qt.io/squish/howto/using-squish-functions-python-modules-packages/ knowledge base article.

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