bdd: Skip tests on WebEngine causing memory leaks

This commit is contained in:
Florian Bruhin 2016-08-18 22:46:32 +02:00
parent 1c581cf1cf
commit 8da942ddc7
2 changed files with 6 additions and 0 deletions

View File

@ -182,6 +182,9 @@ class WebEngineScroller(browsertab.AbstractScroller):
"""QtWebEngine implementations related to scrolling.""" """QtWebEngine implementations related to scrolling."""
# FIXME:qtwebengine
# using stuff here with a big count/argument causes memory leaks and hangs
def __init__(self, tab, parent=None): def __init__(self, tab, parent=None):
super().__init__(tab, parent) super().__init__(tab, parent)
self._pos_perc = (0, 0) self._pos_perc = (0, 0)

View File

@ -121,6 +121,7 @@ Feature: Scrolling
And I run :scroll left And I run :scroll left
Then the page should not be scrolled Then the page should not be scrolled
@qtwebengine_skip: Causes memory leak...
Scenario: Scrolling down with a very big count Scenario: Scrolling down with a very big count
When I run :scroll down with count 99999999999 When I run :scroll down with count 99999999999
# Make sure it doesn't hang # Make sure it doesn't hang
@ -186,6 +187,7 @@ Feature: Scrolling
When I run :scroll-perc with count 50 When I run :scroll-perc with count 50
Then the page should be scrolled vertically Then the page should be scrolled vertically
@qtwebengine_skip: Causes memory leak...
Scenario: :scroll-perc with a very big value Scenario: :scroll-perc with a very big value
When I run :scroll-perc 99999999999 When I run :scroll-perc 99999999999
Then no crash should happen Then no crash should happen
@ -248,6 +250,7 @@ Feature: Scrolling
When I run :scroll-page --top-navigate prev 0 -1 When I run :scroll-page --top-navigate prev 0 -1
Then data/hello3.txt should be loaded Then data/hello3.txt should be loaded
@qtwebengine_skip: Causes memory leak...
Scenario: :scroll-page with a very big value Scenario: :scroll-page with a very big value
When I run :scroll-page 99999999999 99999999999 When I run :scroll-page 99999999999 99999999999
Then the error "Numeric argument is too large for internal int representation." should be shown Then the error "Numeric argument is too large for internal int representation." should be shown