Squish/Custom Settings for Test Runs: Difference between revisions
No edit summary |
(Mark as not-a-category) |
||
| Line 1: | Line 1: | ||
{{Delete|reason=Page not category. Include as single block in [[Squish: custom settings for test runs]] if relevant}} | |||
This page in: [[:Category:Tools::Squish::CustomSettingsForTestRunsSpanish|Español]] [[:Category:Tools::Squish::CustomSettingsForTestRuns_Italian|Italian]] | |||
[[Category:Tools::Squish]] | [[Category:Tools::Squish]] | ||
Revision as of 13:11, 15 September 2016
| This article is nominated for deletion. Reason: Page not category. Include as single block in Squish: custom settings for test runs if relevant Please raise your support/opposition to this nomination in the article's discussion page. |
Custom settings for test runs
In certain test cases, it might be necessary to use custom settings for the application compared to other test cases. This could for example include an application that shows an introductory guide the very first time it is started, to set up some basic settings. This would only work the first time though, as the settings are stored when the test case is finished, preferrably using QSettings.
But since we can access all of the Qt API from Squish, there is an easy way around this problem! For the specific test case, simply modify the QSettings object for the application. Or more specifically, change the path to where the settings are stored to a temporary directory that you are removing at the end of the test script.
tempDir = "/tmp/test-settings"
QSettings.setPath(QSettings.NativeFormat, QSettings.UserScope, tempDir)
Keep in mind that this call will not modify existing QSettings objects in the application, so this will need to be done before any of those are created.