rnhmjoj/qutebrowser
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
83fdb68fc2
qutebrowser/tests/end2end/features/navigate.feature

111 lines
3.8 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:
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
Feature: Using :navigate
Scenario: :navigate with invalid argument
When I run :navigate foo
Use typing.py-like annotations for command args This means: - An annotation like (int, str) is now typing.Union[int, str]. - utils.typing got expanded so it acts like the real typing.py, with issubclass() working properly with typing.Union and __union_params__ being set. - A literal string doesn't exist anymore as annotation, instead @cmdutils.argument now has a 'choices' argument which can be used like @cmdutils.argument('arg', choices=['val1', 'val2']). - Argument validating/converting is now entirely handled by argparser.type_conv instead of relying on python's argparse, i.e. type/choices is now not passed to argparse anymore.
2016-05-11 08:01:25 +02:00
Then the error "where: Invalid value foo - expected one of: prev, next, up, increment, decrement" should be shown
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
# up
Scenario: Navigating up
When I open data/navigate/sub
And I run :navigate up
Then data/navigate should be loaded
add end-to-end tests for navigating with a count
2016-08-16 10:28:31 +02:00
Scenario: Navigating up by count
When I open data/navigate/sub/index.html
And I run :navigate up with count 2
Then data/navigate should be loaded
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
# prev/next
Scenario: Navigating to previous page
When I open data/navigate
And I run :navigate prev
Then data/navigate/prev.html should be loaded
Scenario: Navigating to next page
When I open data/navigate
And I run :navigate next
Then data/navigate/next.html should be loaded
Scenario: Navigating to previous page without links
bdd: Reorganize numbered test files.
2015-11-25 18:02:14 +01:00
When I open data/numbers/1.txt
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
And I run :navigate prev
bdd: Remove trailing dots.
2015-11-26 17:50:39 +01:00
Then the error "No prev links found!" should be shown
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
Scenario: Navigating to next page without links
bdd: Reorganize numbered test files.
2015-11-25 18:02:14 +01:00
When I open data/numbers/1.txt
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
And I run :navigate next
bdd: Remove trailing dots.
2015-11-26 17:50:39 +01:00
Then the error "No forward links found!" should be shown
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
:navigate: command and test feature
2016-04-19 17:00:20 +02:00
Scenario: Navigating to next page to a fragment
When I open data/navigate#fragment
And I run :navigate next
Then data/navigate/next.html should be loaded
Detect rel-attributes on <a> elements for :navigate
2017-02-11 20:48:01 +01:00
Scenario: Navigating to previous page with rel
When I open data/navigate/rel.html
And I run :navigate prev
Then data/navigate/prev.html should be loaded
Scenario: Navigating to next page with rel
When I open data/navigate/rel.html
And I run :navigate next
Then data/navigate/next.html should be loaded
tests navigate: Add tests for rel attributes with nofollow Add two extra tests for checking navigation on pages with rel "next" and "prev" links which are also rel "nofollow" to test for the correct functionality of navigating pages with rel "next" and "prev" links with multiple rel attributes.
2017-02-19 13:32:19 +01:00
Scenario: Navigating to previous page with rel nofollow
When I open data/navigate/rel_nofollow.html
And I run :navigate prev
Then data/navigate/prev.html should be loaded
Scenario: Navigating to next page with rel nofollow
When I open data/navigate/rel_nofollow.html
And I run :navigate next
Then data/navigate/next.html should be loaded
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
# increment/decrement
Scenario: Incrementing number in URL
bdd: Reorganize numbered test files.
2015-11-25 18:02:14 +01:00
When I open data/numbers/1.txt
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
And I run :navigate increment
bdd: Reorganize numbered test files.
2015-11-25 18:02:14 +01:00
Then data/numbers/2.txt should be loaded
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
Scenario: Decrementing number in URL
bdd: Reorganize numbered test files.
2015-11-25 18:02:14 +01:00
When I open data/numbers/4.txt
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
And I run :navigate decrement
bdd: Reorganize numbered test files.
2015-11-25 18:02:14 +01:00
Then data/numbers/3.txt should be loaded
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
Scenario: Decrementing with no number in URL
When I open data/navigate
And I run :navigate decrement
bdd: Remove trailing dots.
2015-11-26 17:50:39 +01:00
Then the error "No number found in URL!" should be shown
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
Scenario: Incrementing with no number in URL
When I open data/navigate
And I run :navigate increment
bdd: Remove trailing dots.
2015-11-26 17:50:39 +01:00
Then the error "No number found in URL!" should be shown
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
add end-to-end tests for navigating with a count
2016-08-16 10:28:31 +02:00
Scenario: Incrementing number in URL by count
When I open data/numbers/3.txt
And I run :navigate increment with count 3
Then data/numbers/6.txt should be loaded
Scenario: Decrementing number in URL by count
When I open data/numbers/8.txt
And I run :navigate decrement with count 5
Then data/numbers/3.txt should be loaded
Add an url. group to settings
2017-07-02 12:07:27 +02:00
Scenario: Setting url.incdec_segments
When I set url.incdec_segments to [anchor]
bdd: Reorganize numbered test files.
2015-11-25 18:02:14 +01:00
And I open data/numbers/1.txt
bdd: Add some tests for :navigate.
2015-11-24 21:32:45 +01:00
And I run :navigate increment
bdd: Remove trailing dots.
2015-11-26 17:50:39 +01:00
Then the error "No number found in URL!" should be shown
end2end testcase for #844
2016-08-04 12:47:14 +02:00
navigate.feature: Add @qtwebengine_todo
2016-08-18 22:23:11 +02:00
@qtwebengine_todo: Doesn't find any elements
end2end testcase for #844
2016-08-04 12:47:14 +02:00
Scenario: Navigating multiline links
When I open data/navigate/multilinelinks.html
And I run :navigate next
Then data/numbers/5.txt should be loaded
Reference in New Issue Copy Permalink