Changes between Version 1 and Version 2 of QtWebKitPerformanceUtilities
- Timestamp:
- Sep 29, 2009, 9:48:41 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
QtWebKitPerformanceUtilities
v1 v2 22 22 === Test Applications === 23 23 ==== An example launcher ==== 24 The example launcher is provided as a simple testing tool to display one website. The to be displayed site can be requested on the command line. 25 24 26 ==== A stress testing application ==== 27 The stress testing application can be found in the '''robustness/''' directory. The application starts with one website and then picks any of the links on the website and navigates to this link. The goal of this application is to provide crashes, load failures, or creating a bad state inside WebCore. 25 28 26 29 === Performance tools === 27 30 ==== The loading test ==== 31 The loading test can be found in the '''loading/''' subdirectory. The goal of this benchmark is to measure and analayse the loading of web pages. The loading is waiting for the ''QWebPage::loadFinished'' signal and the webpage is not shown to avoid to paint the page as painting will be tested separately. 32 33 ==== The painting test ==== 34 The painting test can be found in the '''painting/''' subdirectory. The goal of this benchmark is to measure the painting performance. For this the webpage is loaded and then viewport (first part of the page) is drawn repeatedly to a QPixmap. The painting is finished with a call to ''QApplication::syncX'' which should force the painting to happen. 35 28 36 ==== The scrolling test ==== 29 ==== The painting test ==== 37 The scrolling test can be found in the '''scrolling/''' subdirectory. The goal of this benchmark is to measure the scrolling performance. The benchmark will load the site, wait for it to be loaded. Then it will measure the time it takes to scroll down and up. Scrolling is used as a test as most people reading a website will scroll down to read the text or search for the text. Scrolling will include painting, but depending on the content might also do further JavaScript processing. ''QCoreApplication::processEvents()'' is used after scrolling to force handling of events.
