Squish 6.6 Release Webinar Q&A

Squish 6.6 Release Webinar Q&A

We received lots of great questions on the new features and upgrades in Squish during the Squish 6.6 release webinars. Below, we’ve answered each question received during the Q&A portion.


Scripting Upgrades

Can the Python version be changed after Squish is installed?

Yes. In a command prompt, issue the following:

squishconfig --python=2

To set Python 2. Or,

squishconfig --python=3

To use Python 3.

Our Knowledge Base article includes the above commands and explains how to setup a Squish 6.6 installation to use an external Python interpreter.

Does Squish 6.6 support Python type hints?

Yes. The Python editor in the Squish IDE, from version 6.6 on, is based on PyDev 7.3.0. Among other helpful features, this enables support for type hints in Python 3.


Tagged Execution Improvements

How are tags specified for scenarios in Behavior-Driven Development (BDD) test cases?

Tags for BDD test cases are not specified in the same manner as for script-based test cases. In BDD test cases, the Gherkin file format allows assigning tags to a scenario directly within the feature file.

Please see our Knowledge Base article on adding tags to BDD scenarios for a representative example.

In which file are tags saved?

Tag names and other test configuration settings are stored in the config.xml file, located in your test case folder, i.e.:

suite_mySuite/tst_myTestCase/config.xml

Are test case tags local only, or can they be shared with the code in a Version Control System (VCS)?

Yes they can. Tags are stored in the config.xml file within your test case directory. Add this file to your repository to keep it under version control and share it with other committers.

Do tags work across multiple suites, or are they limited only to a single suite?

Tags are assigned at the test case level. Using identical tags, you can, for example, run test cases from multiple test suites in a single execution step. Our Tip of the Week article, Customizing Which Tests are Executed with the Squish Jenkins Plugin, details this using the Jenkins Continuous Integration server.


Remote Control

Does the remote control feature work only for Qt apps and specific Qt versions?

Remote control in Squish 6.6 is not limited to a specific technology or toolkit version; it was designed to work for virtually any desktop, mobile or embedded target.

What is the performance impact of the remote control feature on the controlled system?

There will be some minor performance impact on your device, with slower systems feeling a greater impact. We’ve developed remote control to minimize performance slowdowns by transmitting data only if there is a change in the device’s display.

If you discover some interference during test execution, we recommend adjusting the frame rate in the Squish Remote Control dialog to improve performance.

Does remote control cause delays in starting the Application Under Test (AUT)?

You should not notice any delays in starting your AUT.

How is communication to hardware on the remote side handled?

The communication to the remote device is embedded into regular data streams between Squish and the AUT process. Our remote control solution talks to the remote operating system and queries the rendering API for the device’s screen contents.

How does Squish know which application it is showing?

Squish shows the content of the device’s display, not a single application. However, Squish does require a running AUT on the remote system.

If there are multiple AUTs running at the same time, then the remote control dialog will show a combo box in which you can select an AUT for display in the viewer.

How do I provide credentials if the remote hardware is login protected?

Remote control requires a running AUT hooked by Squish to operate. It uses the security context of that application to access the remote system, so no further credentials are required.


Qt for WebAssembly Support

Is it required to use Squish for Web for testing Qt for WebAssembly content? Can I use Squish for Qt?

Our webinar demo showed the new support using Squish for Web. The Wasm wrapper can be used with Squish for Qt editions, but there are limitations and some necessary preparatory steps for accessing this content. One limitation being that with Squish for Qt, you cannot access web content created outside of the Qt toolkit.

We encourage you to take a look at our Qt for WebAssembly testing blog which outlines steps for testing apps using Squish for Web or Squish for Qt, within the Qt for WebAssembly context.


.NET Core Support

Where can I find the example applications used in the demo?

The example .NET Core applications shown during the webinar are hosted on GitHub. You can find them, and other examples, here.


Android UI Automation Enhancements

Which version of Android does Squish support?

Squish 6.6 currently supports Android 10.0, Google’s latest major release from September 2019.

Nick joined froglogic Marketing in 2018, following graduate study in computational mechanics and various Application Engineering roles within the software sector. When he’s not blogging for froglogic, he enjoys testing vegan recipes, reading poetry and modding his Subaru.

2 Comments

  1. dipti dilpak 2 months ago

    This information is really useful for us thanks for sharing it

    • Author
      Nicholas Medeiros 2 months ago

      We’re happy it helped! Thanks for your note.

Leave a reply

Your email address will not be published. Required fields are marked *

*