rnhmjoj/qutebrowser
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
6519f500a9
qutebrowser/tests/end2end/features/completion.feature

98 lines
3.5 KiB
Gherkin
Raw Normal View History

Add a modeline to all the *.feature files This really tripped me up yesterday, My "Vim default" is to use tabs. This (where `!···` is a tab) does not work as you'll hope it works: Scenario: Retrying a failed download when the directory didn't exist (issue 2445) When I download http://localhost:(port)/data/downloads/download.bin to <path> And I wait for the error "Download error: No such file or directory: *" And I make the directory <mkdir> And I run :download-retry !···!···And I wait until the download is finished Then the downloaded file <expected> should exist Examples: | path | mkdir | expected | | asd/zxc/ | asd/zxc | asd/zxc/download.bin | Unfortunately, pytest-bdd uses the "Python 2 behaviour" of "expand all tabs to 8 spaces", and doesn't give any errors on strange/inconsistent whitespace. It can cause very confusing errors.
2017-03-31 17:16:31 +02:00
# vim: ft=cucumber fileencoding=utf-8 sts=4 sw=4 et:
Add tests for the completion engine I tested everything that I thought was interesting enough to warrant a test: especially the ability to test multiple parameters deep, as well as testing :set --cycle and some involved example to make sure completion actually works and updates in realtime
2016-08-11 05:15:08 +02:00
Feature: Using completion
Test for completion warnings with 1 item. Add a regression test for #1600: Warnings from completionwidget when it only has 1 item. Addresses #1899.
2016-09-01 04:25:34 +02:00
Scenario: No warnings when completing with one entry (#1600)
Given I open about:blank
When I run :set-cmd-text -s :open
And I run :completion-item-focus next
Then no crash should happen
Fix hang with multiple spaces in URL completion
2016-09-04 20:19:16 +02:00
Scenario: Hang with many spaces in completion (#1919)
# Generate some history data
When I open data/numbers/1.txt
And I open data/numbers/2.txt
And I open data/numbers/3.txt
And I open data/numbers/4.txt
And I open data/numbers/5.txt
And I open data/numbers/6.txt
And I open data/numbers/7.txt
And I open data/numbers/8.txt
And I open data/numbers/9.txt
And I open data/numbers/10.txt
And I run :set-cmd-text :open a b
# Make sure qutebrowser doesn't hang
And I run :message-info "Still alive!"
Then the message "Still alive!" should be shown
Handle unicode characters in Completer. Just limit the cursor position to the length of the text to avoid crashes in this case. Resolves #2007.
2016-10-04 13:36:49 +02:00
Scenario: Crash when pasting emoji into the command line (#2007)
Given I open about:blank
When I run :set-cmd-text -s :🌀
Then no crash should happen
Add tests for the completion engine I tested everything that I thought was interesting enough to warrant a test: especially the ability to test multiple parameters deep, as well as testing :set --cycle and some involved example to make sure completion actually works and updates in realtime
2016-08-11 05:15:08 +02:00
Scenario: Using command completion
When I run :set-cmd-text :
Fix end2end completion tests for SQL backend. Change the logging to report the completion function name and have the end2end tests check for this. Remove the tests for realtime completion, as it was decided this is not an important feature and the code is much simpler without it.
2017-02-16 03:29:00 +01:00
Then the completion model should be command
Add tests for the completion engine I tested everything that I thought was interesting enough to warrant a test: especially the ability to test multiple parameters deep, as well as testing :set --cycle and some involved example to make sure completion actually works and updates in realtime
2016-08-11 05:15:08 +02:00
Scenario: Using help completion
When I run :set-cmd-text -s :help
Fix end2end completion tests for SQL backend. Change the logging to report the completion function name and have the end2end tests check for this. Remove the tests for realtime completion, as it was decided this is not an important feature and the code is much simpler without it.
2017-02-16 03:29:00 +01:00
Then the completion model should be helptopic
Add tests for the completion engine I tested everything that I thought was interesting enough to warrant a test: especially the ability to test multiple parameters deep, as well as testing :set --cycle and some involved example to make sure completion actually works and updates in realtime
2016-08-11 05:15:08 +02:00
Scenario: Using quickmark completion
When I run :set-cmd-text -s :quickmark-load
Fix end2end completion tests for SQL backend. Change the logging to report the completion function name and have the end2end tests check for this. Remove the tests for realtime completion, as it was decided this is not an important feature and the code is much simpler without it.
2017-02-16 03:29:00 +01:00
Then the completion model should be quickmark
Add tests for the completion engine I tested everything that I thought was interesting enough to warrant a test: especially the ability to test multiple parameters deep, as well as testing :set --cycle and some involved example to make sure completion actually works and updates in realtime
2016-08-11 05:15:08 +02:00
Scenario: Using bookmark completion
When I run :set-cmd-text -s :bookmark-load
Fix end2end completion tests for SQL backend. Change the logging to report the completion function name and have the end2end tests check for this. Remove the tests for realtime completion, as it was decided this is not an important feature and the code is much simpler without it.
2017-02-16 03:29:00 +01:00
Then the completion model should be bookmark
Add tests for the completion engine I tested everything that I thought was interesting enough to warrant a test: especially the ability to test multiple parameters deep, as well as testing :set --cycle and some involved example to make sure completion actually works and updates in realtime
2016-08-11 05:15:08 +02:00
Scenario: Using bind completion
When I run :set-cmd-text -s :bind X
Fix end2end completion tests for SQL backend. Change the logging to report the completion function name and have the end2end tests check for this. Remove the tests for realtime completion, as it was decided this is not an important feature and the code is much simpler without it.
2017-02-16 03:29:00 +01:00
Then the completion model should be bind
Add tests for the completion engine I tested everything that I thought was interesting enough to warrant a test: especially the ability to test multiple parameters deep, as well as testing :set --cycle and some involved example to make sure completion actually works and updates in realtime
2016-08-11 05:15:08 +02:00
Add macOS xfail for session completion test See #2956
2017-09-11 16:54:39 +02:00
# See #2956
Only mark completion issue as flaky
2017-09-11 19:33:27 +02:00
@flaky
Add tests for the completion engine I tested everything that I thought was interesting enough to warrant a test: especially the ability to test multiple parameters deep, as well as testing :set --cycle and some involved example to make sure completion actually works and updates in realtime
2016-08-11 05:15:08 +02:00
Scenario: Using session completion
Given I open data/hello.txt
And I run :session-save hello
When I run :set-cmd-text -s :session-load
And I run :completion-item-focus next
And I run :completion-item-focus next
And I run :session-delete hello
And I run :command-accept
Then the error "Session hello not found!" should be shown
Scenario: Using option completion
Fix completion tests after config merge.
2017-08-12 21:07:17 +02:00
When I run :set-cmd-text -s :set
Fix end2end completion tests for SQL backend. Change the logging to report the completion function name and have the end2end tests check for this. Remove the tests for realtime completion, as it was decided this is not an important feature and the code is much simpler without it.
2017-02-16 03:29:00 +01:00
Then the completion model should be option
Add tests for the completion engine I tested everything that I thought was interesting enough to warrant a test: especially the ability to test multiple parameters deep, as well as testing :set --cycle and some involved example to make sure completion actually works and updates in realtime
2016-08-11 05:15:08 +02:00
Scenario: Using value completion
Fix completion tests after config merge.
2017-08-12 21:07:17 +02:00
When I run :set-cmd-text -s :set aliases
Fix end2end completion tests for SQL backend. Change the logging to report the completion function name and have the end2end tests check for this. Remove the tests for realtime completion, as it was decided this is not an important feature and the code is much simpler without it.
2017-02-16 03:29:00 +01:00
Then the completion model should be value
Add tests for the completion engine I tested everything that I thought was interesting enough to warrant a test: especially the ability to test multiple parameters deep, as well as testing :set --cycle and some involved example to make sure completion actually works and updates in realtime
2016-08-11 05:15:08 +02:00
Scenario: Deleting an open tab via the completion
Given I have a fresh instance
When I open data/hello.txt
And I open data/hello2.txt in a new tab
And I run :set-cmd-text -s :buffer
Try stabilizing completion test
2017-10-05 20:03:35 +02:00
And I wait for "Setting completion pattern ''" in the log
Add tests for the completion engine I tested everything that I thought was interesting enough to warrant a test: especially the ability to test multiple parameters deep, as well as testing :set --cycle and some involved example to make sure completion actually works and updates in realtime
2016-08-11 05:15:08 +02:00
And I run :completion-item-focus next
Try to stabilize :completion-item-del for :buffer test
2017-10-04 09:08:59 +02:00
And I wait for "setting text = ':buffer 0/1', *" in the log
Add tests for the completion engine I tested everything that I thought was interesting enough to warrant a test: especially the ability to test multiple parameters deep, as well as testing :set --cycle and some involved example to make sure completion actually works and updates in realtime
2016-08-11 05:15:08 +02:00
And I run :completion-item-focus next
Try to stabilize :completion-item-del for :buffer test
2017-10-04 09:08:59 +02:00
And I wait for "setting text = ':buffer 0/2', *" in the log
Add tests for the completion engine I tested everything that I thought was interesting enough to warrant a test: especially the ability to test multiple parameters deep, as well as testing :set --cycle and some involved example to make sure completion actually works and updates in realtime
2016-08-11 05:15:08 +02:00
And I run :completion-item-del
Then the following tabs should be open:
- data/hello.txt (active)
Fixed problems with tab completion after moving tabs (#2141)
2016-11-30 13:35:08 +01:00
Scenario: Go to tab after moving a tab
Given I have a fresh instance
When I open data/hello.txt
And I open data/hello2.txt in a new tab
# Tricking completer into not updating tabs
And I run :set-cmd-text -s :buffer
And I run :tab-move 1
And I run :buffer hello2.txt
Then the following tabs should be open:
- data/hello2.txt (active)
- data/hello.txt
Reference in New Issue Copy Permalink