summaryrefslogtreecommitdiffstats
path: root/tests/auto/core/tests.pri
Commit message (Collapse)AuthorAgeFilesLines
* Fix QWebEngineUrlRequestInfo::firstPartyUrl() after 69-basedTamas Zakor2019-01-031-0/+2
| | | | | | | | | | | | | | The issue was introduced by this Chromium change: https://chromium-review.googlesource.com/c/chromium/src/+/1025772/ Add new auto tests for first party url. Depends on Chromium change: d2f5d6869f Add net::URLRequest::first_party_url() Task-number: QTBUG-70790 Change-Id: Ib43bde69990e7fb1d495cc32ac2f6860a613f185 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Chromium requires C++14Allan Sandfeld Jensen2018-10-111-1/+0
| | | | | | | | | QtWebEngineCore was only building because Chromium CPPFLAGS was overriding ours. And setting C++11 in our examples and tests now forces a downgrade. Change-Id: I3642394f15bb9974688991800552624d2379faf9 Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Fix font load error messages inside non-app-bundle testsAlexandru Croitor2017-01-101-1/+2
| | | | | | | | | | | | | | | Some fonts were failing to load in tests because macOS does not consider some font paths when an application is built without an Info.plist file (as is the case for a non-bundle application). It is possible though to embed a plist file into the executable by passing the path to the file as a linker argument. This change generates an Info.plist for each test, and embeds it into the final executable, thus fixing the font problems. Task-number: QTBUG-57354 Change-Id: I4c3c29442b9d308ee6a327645054a67c4b008ef8 Reviewed-by: Jake Petroules <jake.petroules@qt.io>
* enable tests/auto/coreJoerg Bornemann2015-10-301-3/+1
| | | | | | | | Enable autotests and blacklist tests that are known to fail. Add skips and waits and mark them with the corresponding task numbers. Change-Id: I993e366ba3b07239a8ba15eae2ee8e3e2aaa8308 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>
* fix automatic resource file inclusionJoerg Bornemann2015-08-261-1/+1
| | | | | | | | | Commit c7334fbc broke the automatic resource file inclusion. qmake's exists function checks at the location of the .pri file, not the location of the .pro file. Change-Id: I54f1bc664c06c5675ef26341619142bc58f0831e Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
* move automatic resource inclusion to pri filesJoerg Bornemann2015-08-251-0/+2
| | | | | | | Avoid code duplication. Change-Id: Icd270ff4e45112111b7eb9590e415947f63ce15b Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
* do not define TESTS_SOURCE_DIR in core testsJoerg Bornemann2015-08-251-3/+0
| | | | | | | It's currently unused, and we can use QFINDTESTDATA instead. Change-Id: Id439b8b6ea3c9dbf5299c271d3974c11a44675bc Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
* Add cookie API testsAndras Becsi2015-07-161-0/+18
This tests the part of the cookie API that can be tested locally. The notification about third-party cookies (acceptCookieFromUrl) can not be tested locally since it requires cookies to be set from a different domain than the main frame, which requires a remote host or a local web server with support for virtual DNS. Testing requires the ability to set cookies for local pages loaded through the qrc scheme. We could eventually extend this in the future to enable setting cookies on registered custom schemes, but for that we might have to implement our own cookie store. Since Chromium's cookie store relies on source url's to manage cookies and qrc:// cookies do not specify a domain, a specific source url is needed to be able to delete an individual cookie that has been set by a page loaded through qrc://. This patch requires a new function on QNetworkCookie to be able to forward the source url of the cookie to Chromium. Change-Id: I97dd04b27fbb8ec63060f9b741ad65c29a773a6c Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-24 16:46:07 +0000