summaryrefslogtreecommitdiffstats
path: root/tests/auto/quick/quick.pro
Commit message (Collapse)AuthorAgeFilesLines
* Enable qquickwebengineviewgraphics test in CIJoerg Bornemann2016-07-081-3/+6
| | | | | | | | | This test requires the QtQuick test support API. Exclude it from build if the API isn't available. Blacklist one problematic test case. Remove the - now superfluous - ENABLE_QML_TESTSUPPORT_API checks. Change-Id: I0b36de182628969e1185d685fa098d6140ae8d9c Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* OS X: Fix crash when setting a custom default QSurfaceFormat.Alexandru Croitor2016-02-041-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Setting a new default QSurfaceFormat after QtWebEngineCore::initialize() is called, might lead to a crash. This happens when the new surface format has a different OpenGL profile, compared to the profile created by web engine in the RenderWidgetHostViewQtDelegateWidget constructor. The default constructed QSurfaceFormat has an OpenGL Compatibility profile. Inside the Cocoa platform plugin when a new shared OpenGL context is created, it fails to initialize the new context because of the difference in profiles, and thus ultimately creates an unshared context, which leads to a crash. Fix consists in using the shared context QSurfaceFormat in the RenderWidgetHostViewQtDelegateWidget constructor, and also printing a fatal warning to notify the developer only to set the new QSurfaceFormat before the application instance is declared. Bottom line, if the QSurfaceFormat OpenGL profile has to be changed, it should be done before QtWebEngineCore::initialize() is called. Doing so after initialize() is called, will lead to a crash. Change-Id: I8a07211b592143d736b001556b944d4759802396 Task-number: QTBUG-50665 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com> Reviewed-by: Michal Klocek <michal.klocek@theqtcompany.com>
* Build qmltests only if QML testsupport API is availableJoerg Bornemann2015-12-111-1/+2
| | | | | Change-Id: Id54356024f60e5f877271b29895912e2bf0cb84f Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>
* Import the inspectorserver auto test from qtwebkitJocelyn Turcotte2015-01-221-0/+1
| | | | | | | | The command interface is still similar to the remote inspector in WebKit2, the JSON page list information is slightly different. Change-Id: I85e6bd665efe9ba487622ec0f5c2e66669526888 Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
* Import QQuickWebEngineView API testSzabolcs David2014-10-141-0/+1
| | | | | | | | Add crash tests for the Quick API and mark the unimplemented features in the test logs. Change-Id: I8e6b322fb1bb5ed75fed8b9556e2e975c9227f0a Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Fix typos and warnings in the Quick testsSzabolcs David2014-06-051-1/+1
| | | | | | | | | - Add valid size to tst_faviconLoad.qml - Add missing files to qmltests.pro - Rename test cases and files from WebView to WebEngineView Change-Id: I40163117a11672b18230046a1604624bc4620dba Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Get rid of the BackingStore rendering pathJocelyn Turcotte2014-04-081-5/+3
| | | | | | | | | Now that the widgets view is also using the delegated renderer, there are no supported configuration that use the BackingStore rendering path, itself on the way of deprecation in Chromium. Change-Id: I4ab889f6a7c65e8447c259faf2c7a98b88c1acf5 Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
* Add public API test to Quick API.Szabolcs David2014-02-171-0/+1
| | | | | | | | | | | | This test checks the compatibility of WebEngineView and QtWebKit's WebView. (The differences are marked as expected failure.) The QQuickWebEngineNavigationRequest class has not been implemented yet. Change-Id: Ie03d605b06d141c6ca352ae1cd5c6a38f4c80039 Reviewed-by: Andras Becsi <andras.becsi@digia.com> Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
* Add QML test framework and titleChanged test caseAdam Kallai2014-01-201-0/+1
| | | | | | | Change-Id: Ie38ee02e485702d10d0c171f2168f2685c2de2a6 Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu> Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com> Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Fix the build with Qt 5.1Andras Becsi2013-11-261-1/+2
| | | | | | | | We are still able to build with Qt 5.1 if we disable the hardware acceleration codepaths. Change-Id: Ic748dac0a7f25bbd79f2f711a18431872cebd917 Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
* Add some QQuickWebView graphics stack tests.Jocelyn Turcotte2013-11-151-0/+5
This does basic sanity testing of the graphics stack for both the hardware accelerated and software codepaths. This also adds a required signal to report the CompositingSurface later on if the QWindow wasn't available yet when Chromium asked for it. Change-Id: I402ec5ade9114c78bea7960c5f0de989f54110e3 Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>