summaryrefslogtreecommitdiff
path: root/tests/auto/positionplugin/plugin.json
Commit message (Collapse)AuthorAgeFilesLines
* Remove QtPositioning module from qtlocation.git6.2.46.2.36.2.26.2Ivan Solovev2021-11-021-9/+0
| | | | | | | | | | | | | | | Turns out that our CI does not support repos without any tests. This is treated like an error and leads to integration failure. This patch fixes it by disabling tests in coin/module_config.yaml. This config should be fixed when QtLocation tests are enabled Task-number: QTBUG-97084 Change-Id: Ib06e865fe2836806bbbee34345f06b471dd48660 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Alex Blasche <alexander.blasche@qt.io> (cherry picked from commit 23f32792ad53e23bbafbff6d7667f0bb0f69fc53)
* QGeoPositionInfoSource: fix flaky testIvan Solovev2021-05-171-1/+1
| | | | | | | | | | | | | | | | | | | | When introducing a dummy.source plugin for the tests, the priority was selected the same, as for the test.source plugin. As a result, the algorithm for selecting the default source during the test run could pick any of them. When dummy.source was picked, the preferredMethodsBinding test could not execute correctly, because the dummy.source has different supported positioning methods. This patch fixes the problem in 2 ways: * test.source is now directly selected in the preferredMethodsBinding() test * the priorities of the dummy.source and test.source plugins are adjusted in such a way, that test.source is picked if createDefaultSource() call is used. Change-Id: Ibec456f4679207a161c2cf97c267055d75bbd03c Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
* Add tests for PluginParameters in PositionSourcePaolo Angelelli2019-07-241-1/+1
| | | | | | | | | Testing parameters in QGeoPositionInfoSourceFactory becomes implicit with this test. Task-number: QTBUG-66304 Change-Id: I3e9fbf99762e9a03e4c8cae3ff317ea36313e687 Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
* Skip loading real plugins in testsLaszlo Agocs2015-09-091-1/+2
| | | | | | | | | | Introduce a new plugin metadata field "Testable" that can be used to indicate that using the plugin in question in test runs (e.g. in a CI environment) is dangerous. We can then check for QT_QTESTLIB_RUNNING and skip the plugin in question. Change-Id: Iabe9f1600d7274e0e9224dc49d02aa2e5d3cabd6 Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
* QGeoAreaMonitor becomes loadable via plugins.Alex Blasche2013-08-221-0/+1
| | | | | | | | | The polling-based default implementation is separated out into its own plugin. Task-number: QTBUG-31960 Change-Id: Ife25f6a83dd51f32fcd9ee3bfde1ca51291c78e4 Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
* Update positioning sources to use new plugin styleAlex Wilson2012-03-121-0/+7
Notably, also splits the default sources that were previously compiled into the library, out into their own plugins. This follows a similar pattern to the geoservices change. We also drop the "plugin whitelisting" feature in favour of a simple Priority value in the plugin JSON -- the whitelist provides no additional security over this solution on any of our platforms. Task-number: QTBUG-24331 Change-Id: I62a9c940157ad2e33a9a575fa09633b98656b276 Reviewed-by: Alex <alex.blasche@nokia.com>