Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.
Squish/Waiting for Input from the Test Operator: Difference between revisions
< Squish
Jump to navigation
Jump to search
(Mark as not-a-category) |
AutoSpider (talk | contribs) m (AutoSpider moved page Category:Tools::Squish::Waiting for input from the test operator to Squish/Waiting for Input from the Test Operator: Title name format) |
Revision as of 02:56, 25 November 2017
This article is nominated for deletion. Reason: Page not category. Include as single block in Squish: waiting for input from the test operator if relevant Please raise your support/opposition to this nomination in the article's discussion page. |
Waiting for input from the test operator
In the cases where Squish cannot automate the whole test case, such as when a coin needs to be inserted into a slot machine or a physical button needs to be pressed which Squish cannot simulate, you need some way of notifying the test operator. As we have access to the whole Qt API from Squish, this can easily be done with a QMessageBox:
QMessageBox.information(0, "Input needed", "Please insert coin now!")<code>
As the call to information() won't return until the user clicks the OK button, the script will be paused until that happens.
We can also use Squish's powerful waitFor() command to continue the script immediately when the required action has occurred, without the user having to click a button, which can be useful in situations where an input cursor is not available for the test operator:
label = QLabel("Please insert coin now!")
label.show()
waitFor("findObject(':CoinCounter_QLabel').text == '1'")
label.close()