be07107b1c
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.
93 lines
3.3 KiB
Gherkin
93 lines
3.3 KiB
Gherkin
# vim: ft=cucumber fileencoding=utf-8 sts=4 sw=4 et:
|
|
|
|
Feature: Using completion
|
|
|
|
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
|
|
|
|
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
|
|
|
|
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
|
|
|
|
Scenario: Using command completion
|
|
When I run :set-cmd-text :
|
|
Then the completion model should be command
|
|
|
|
Scenario: Using help completion
|
|
When I run :set-cmd-text -s :help
|
|
Then the completion model should be helptopic
|
|
|
|
Scenario: Using quickmark completion
|
|
When I run :set-cmd-text -s :quickmark-load
|
|
Then the completion model should be quickmark
|
|
|
|
Scenario: Using bookmark completion
|
|
When I run :set-cmd-text -s :bookmark-load
|
|
Then the completion model should be bookmark
|
|
|
|
Scenario: Using bind completion
|
|
When I run :set-cmd-text -s :bind X
|
|
Then the completion model should be bind
|
|
|
|
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
|
|
When I run :set-cmd-text -s :set colors
|
|
Then the completion model should be option
|
|
|
|
Scenario: Using value completion
|
|
When I run :set-cmd-text -s :set colors statusbar.bg
|
|
Then the completion model should be value
|
|
|
|
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
|
|
And I run :completion-item-focus next
|
|
And I run :completion-item-focus next
|
|
And I run :completion-item-del
|
|
Then the following tabs should be open:
|
|
- data/hello.txt (active)
|
|
|
|
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
|