bdd: Add qtwebengine tags in misc.feature
This commit is contained in:
Florian Bruhin
parent
ec59bfb584
commit
25faa04196
@ -190,6 +190,7 @@ Feature: Various utility commands.
|
||||
|
||||
# :view-source
|
||||
|
||||
@qtwebengine_skip: Flaky due to :view-source being async
|
||||
Scenario: :view-source
|
||||
Given I open data/hello.txt
|
||||
When I run :tab-only
|
||||
@ -204,6 +205,7 @@ Feature: Various utility commands.
|
||||
history: []
|
||||
And the page source should look like misc/hello.txt.html
|
||||
|
||||
@qtwebengine_skip: Flaky due to :view-source being async
|
||||
Scenario: :view-source on source page.
|
||||
When I open data/hello.txt
|
||||
And I run :view-source
|
||||
@ -222,6 +224,7 @@ Feature: Various utility commands.
|
||||
|
||||
# :help
|
||||
|
||||
@qtwebengine_todo: :help is not implemented yet
|
||||
Scenario: :help without topic
|
||||
When I run :tab-only
|
||||
And I run :help
|
||||
@ -233,6 +236,7 @@ Feature: Various utility commands.
|
||||
When I run :help foo
|
||||
Then the error "Invalid help topic foo!" should be shown
|
||||
|
||||
@qtwebengine_todo: :help is not implemented yet
|
||||
Scenario: :help with command
|
||||
When the documentation is up to date
|
||||
And I run :tab-only
|
||||
@ -245,6 +249,7 @@ Feature: Various utility commands.
|
||||
When I run :help :foo
|
||||
Then the error "Invalid command foo!" should be shown
|
||||
|
||||
@qtwebengine_todo: :help is not implemented yet
|
||||
Scenario: :help with setting
|
||||
When the documentation is up to date
|
||||
And I run :tab-only
|
||||
@ -265,6 +270,7 @@ Feature: Various utility commands.
|
||||
When I run :help general->bar
|
||||
Then the error "Invalid option bar!" should be shown
|
||||
|
||||
@qtwebengine_todo: :help is not implemented yet
|
||||
Scenario: :help with -t
|
||||
When I open about:blank
|
||||
And I run :tab-only
|
||||
@ -288,18 +294,21 @@ Feature: Various utility commands.
|
||||
|
||||
# pdfjs support
|
||||
|
||||
@qtwebengine_todo: pdfjs is not implemented yet
|
||||
Scenario: pdfjs is used for pdf files
|
||||
Given pdfjs is available
|
||||
When I set content -> enable-pdfjs to true
|
||||
And I open data/misc/test.pdf
|
||||
Then the javascript message "PDF * [*] (PDF.js: *)" should be logged
|
||||
|
||||
@qtwebengine_todo: pdfjs is not implemented yet
|
||||
Scenario: pdfjs is not used when disabled
|
||||
When I set content -> enable-pdfjs to false
|
||||
And I set storage -> prompt-download-directory to false
|
||||
And I open data/misc/test.pdf
|
||||
Then "Download finished" should be logged
|
||||
|
||||
@qtwebengine_todo: pdfjs is not implemented yet
|
||||
Scenario: Downloading a pdf via pdf.js button (issue 1214)
|
||||
Given pdfjs is available
|
||||
# WORKAROUND to prevent the "Painter ended with 2 saved states" warning
|
||||
@ -339,6 +348,8 @@ Feature: Various utility commands.
|
||||
And I run :debug-pyeval QApplication.instance().activeModalWidget().close()
|
||||
Then no crash should happen
|
||||
|
||||
# FIXME:qtwebengine use a finer skipping here
|
||||
@qtwebengine_skip: printing to pdf is not implemented with older Qt versions
|
||||
Scenario: print --pdf
|
||||
When I open data/hello.txt
|
||||
And I run :print --pdf (tmpdir)/hello.pdf
|
||||
@ -346,12 +357,13 @@ Feature: Various utility commands.
|
||||
Then the PDF hello.pdf should exist in the tmpdir
|
||||
|
||||
# :pyeval
|
||||
|
||||
@qtwebengine_todo: qute:pyeval is not implemented yet
|
||||
Scenario: Running :pyeval
|
||||
When I run :debug-pyeval 1+1
|
||||
And I wait until qute:pyeval is loaded
|
||||
Then the page should contain the plaintext "2"
|
||||
|
||||
@qtwebengine_todo: qute:pyeval is not implemented yet
|
||||
Scenario: Causing exception in :pyeval
|
||||
When I run :debug-pyeval 1/0
|
||||
And I wait until qute:pyeval is loaded
|
||||
@ -370,6 +382,7 @@ Feature: Various utility commands.
|
||||
Then no crash should happen
|
||||
|
||||
@pyqt>=5.3.1
|
||||
@qtwebengine_todo: JS prompt is not implemented yet
|
||||
Scenario: Focusing download widget via Tab (original issue)
|
||||
When I open data/prompt/jsprompt.html
|
||||
And I run :click-element id button
|
||||
@ -380,6 +393,7 @@ Feature: Various utility commands.
|
||||
|
||||
## Custom headers
|
||||
|
||||
@qtwebengine_todo: Custom headers are not implemented yet
|
||||
Scenario: Setting a custom header
|
||||
When I set network -> custom-headers to {"X-Qute-Test": "testvalue"}
|
||||
And I open headers
|
||||
@ -387,6 +401,7 @@ Feature: Various utility commands.
|
||||
|
||||
## :messages
|
||||
|
||||
@qtwebengine_todo: qute:log is not implemented yet
|
||||
Scenario: Showing error messages
|
||||
When I run :message-error the-error-message
|
||||
And I run :message-warning the-warning-message
|
||||
@ -399,6 +414,7 @@ Feature: Various utility commands.
|
||||
And the page should not contain the plaintext "the-warning-message"
|
||||
And the page should not contain the plaintext "the-info-message"
|
||||
|
||||
@qtwebengine_todo: qute:log is not implemented yet
|
||||
Scenario: Showing messages of type 'warning' or greater
|
||||
When I run :message-error the-error-message
|
||||
And I run :message-warning the-warning-message
|
||||
@ -411,6 +427,7 @@ Feature: Various utility commands.
|
||||
And the page should contain the plaintext "the-warning-message"
|
||||
And the page should not contain the plaintext "the-info-message"
|
||||
|
||||
@qtwebengine_todo: qute:log is not implemented yet
|
||||
Scenario: Showing messages of type 'info' or greater
|
||||
When I run :message-error the-error-message
|
||||
And I run :message-warning the-warning-message
|
||||
@ -423,24 +440,29 @@ Feature: Various utility commands.
|
||||
And the page should contain the plaintext "the-warning-message"
|
||||
And the page should contain the plaintext "the-info-message"
|
||||
|
||||
@qtwebengine_skip: Flaky for some reason?
|
||||
Scenario: Showing messages of an invalid level
|
||||
When I run :messages cataclysmic
|
||||
Then the error "Invalid log level cataclysmic!" should be shown
|
||||
|
||||
@qtwebengine_todo: qute:log is not implemented yet
|
||||
Scenario: Using qute:log directly
|
||||
When I open qute:log
|
||||
Then no crash should happen
|
||||
|
||||
@qtwebengine_todo: qute:log is not implemented yet
|
||||
Scenario: Using qute:plainlog directly
|
||||
When I open qute:plainlog
|
||||
Then no crash should happen
|
||||
|
||||
@qtwebengine_todo: qute:log is not implemented yet
|
||||
Scenario: Using :messages without messages
|
||||
Given I have a fresh instance
|
||||
When I run :messages
|
||||
Then qute://log?level=error should be loaded
|
||||
And the page should contain the plaintext "No messages to show."
|
||||
|
||||
@qtwebengine_todo: qute:log is not implemented yet
|
||||
Scenario: Using :debug-log-capacity
|
||||
When I run :debug-log-capacity 100
|
||||
And I run :message-info oldstuff
|
||||
@ -472,6 +494,7 @@ Feature: Various utility commands.
|
||||
|
||||
## https://github.com/The-Compiler/qutebrowser/issues/1219
|
||||
|
||||
@qtwebengine_todo: private browsing is not implemented yet
|
||||
Scenario: Sharing cookies with private browsing
|
||||
When I set general -> private-browsing to true
|
||||
And I open cookies/set?qute-test=42 without waiting
|
||||
@ -481,6 +504,7 @@ Feature: Various utility commands.
|
||||
|
||||
## https://github.com/The-Compiler/qutebrowser/issues/1742
|
||||
|
||||
@qtwebengine_todo: private browsing is not implemented yet
|
||||
Scenario: Private browsing is activated in QtWebKit without restart
|
||||
When I set general -> private-browsing to true
|
||||
And I open data/javascript/localstorage.html
|
||||
|
||||
Loading…
Reference in New Issue
Block a user