rnhmjoj/qutebrowser
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
8af5cfb4ac
qutebrowser/tests/end2end/features/spawn.feature

58 lines
2.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 BDD tests for spawn command Issue-Link: https://github.com/The-Compiler/qutebrowser/issues/999
2016-03-25 18:19:35 +01:00
Feature: :spawn
Scenario: Running :spawn
fix spawn tests on Windows On Windows, no echo.exe exists normally, so calling echo from the tests is no good idea, since it relies on Cygwin to be installed and in %PATH% (so that echo.exe is available). This fixes this by providing a small echo.bat which is callable from the tests, and then using a platform-specific path to the executable instead of the hardcoded "echo". This should ensure that the tests pass even on systems where echo.exe is not installed. Note that we can't simply use a do-nothing exe (like rundll or hh.exe), as we're passing parameters, and those executables may behave differently in the presence of those parameters.
2016-09-08 23:14:10 +02:00
When I run :spawn -v (echo-exe) "Hello"
Add BDD tests for spawn command Issue-Link: https://github.com/The-Compiler/qutebrowser/issues/999
2016-03-25 18:19:35 +01:00
Then the message "Command exited successfully." should be shown
Scenario: Running :spawn with command that does not exist
When I run :spawn command_does_not_exist127623
Then the error "Error while spawning command: The process failed to start." should be shown
bdd: Merge userscripts.feature into spawn.feature
2016-05-29 18:24:34 +02:00
Scenario: Starting a userscript which doesn't exist
When I run :spawn -u this_does_not_exist
revised missing userscript error messages
2016-09-30 09:39:14 +02:00
Then the error "Userscript 'this_does_not_exist' not found in userscript directories *" should be shown
improved error messages for inexistent userscripts fixes #1940
2016-09-29 13:29:39 +02:00
Scenario: Starting a userscript with absoloute path which doesn't exist
When I run :spawn -u /this_does_not_exist
Then the error "Userscript '/this_does_not_exist' not found" should be shown
bdd: Merge userscripts.feature into spawn.feature
2016-05-29 18:24:34 +02:00
Replace all GitHub links
2017-02-05 00:13:11 +01:00
# https://github.com/qutebrowser/qutebrowser/issues/1614
tests: Skip :spawn with invalid quoting on Windows For some reason this often causes segfaults lately - let's skip it until we can investigate what's wrong. See #1614
2016-07-03 17:32:19 +02:00
@posix
Add BDD tests for spawn command Issue-Link: https://github.com/The-Compiler/qutebrowser/issues/999
2016-03-25 18:19:35 +01:00
Scenario: Running :spawn with invalid quoting
Try not to confuse syntax highlighting with quotes
2016-03-28 23:53:26 +02:00
When I run :spawn ""'""
Add BDD tests for spawn command Issue-Link: https://github.com/The-Compiler/qutebrowser/issues/999
2016-03-25 18:19:35 +01:00
Then the error "Error while splitting command: No closing quotation" should be shown
Scenario: Running :spawn with url variable
fix spawn tests on Windows On Windows, no echo.exe exists normally, so calling echo from the tests is no good idea, since it relies on Cygwin to be installed and in %PATH% (so that echo.exe is available). This fixes this by providing a small echo.bat which is callable from the tests, and then using a platform-specific path to the executable instead of the hardcoded "echo". This should ensure that the tests pass even on systems where echo.exe is not installed. Note that we can't simply use a do-nothing exe (like rundll or hh.exe), as we're passing parameters, and those executables may behave differently in the presence of those parameters.
2016-09-08 23:14:10 +02:00
When I run :spawn (echo-exe) {url}
Then "Executing * with args ['about:blank'], userscript=False" should be logged
Add basic test for spawning userscripts
2016-03-25 18:21:38 +01:00
Add tests for {url:pretty} variable
2016-04-20 16:58:14 +02:00
Scenario: Running :spawn with url variable in fully encoded format
When I open data/title with spaces.html
fix spawn tests on Windows On Windows, no echo.exe exists normally, so calling echo from the tests is no good idea, since it relies on Cygwin to be installed and in %PATH% (so that echo.exe is available). This fixes this by providing a small echo.bat which is callable from the tests, and then using a platform-specific path to the executable instead of the hardcoded "echo". This should ensure that the tests pass even on systems where echo.exe is not installed. Note that we can't simply use a do-nothing exe (like rundll or hh.exe), as we're passing parameters, and those executables may behave differently in the presence of those parameters.
2016-09-08 23:14:10 +02:00
And I run :spawn (echo-exe) {url}
Then "Executing * with args ['http://localhost:(port)/data/title%20with%20spaces.html'], userscript=False" should be logged
Add tests for {url:pretty} variable
2016-04-20 16:58:14 +02:00
Scenario: Running :spawn with url variable in pretty decoded format
When I open data/title with spaces.html
fix spawn tests on Windows On Windows, no echo.exe exists normally, so calling echo from the tests is no good idea, since it relies on Cygwin to be installed and in %PATH% (so that echo.exe is available). This fixes this by providing a small echo.bat which is callable from the tests, and then using a platform-specific path to the executable instead of the hardcoded "echo". This should ensure that the tests pass even on systems where echo.exe is not installed. Note that we can't simply use a do-nothing exe (like rundll or hh.exe), as we're passing parameters, and those executables may behave differently in the presence of those parameters.
2016-09-08 23:14:10 +02:00
And I run :spawn (echo-exe) {url:pretty}
Then "Executing * with args ['http://localhost:(port)/data/title with spaces.html'], userscript=False" should be logged
Add tests for {url:pretty} variable
2016-04-20 16:58:14 +02:00
Do a final userscript command read on cleanup On OS X, sometimes the userscript exited before the QSocketNotifier was triggered. By doing a final read when cleaning up we make sure we don't miss anything. Fixes #1533.
2016-05-29 18:35:43 +02:00
@posix
Add basic test for spawning userscripts
2016-03-25 18:21:38 +01:00
Scenario: Running :spawn with userscript
Add tests for {url:pretty} variable
2016-04-20 16:58:14 +02:00
When I open about:blank
bdd: Get rid of "I execute the userscript" step Since we now have a (testdata) substitution this is much easier.
2016-05-30 16:21:32 +02:00
And I run :spawn -u (testdata)/userscripts/open_current_url
Add basic test for spawning userscripts
2016-03-25 18:21:38 +01:00
And I wait until about:blank is loaded
Then the following tabs should be open:
- about:blank
- about:blank (active)
style fixes
2016-09-06 20:33:48 +02:00
add an userscript test for Windows
2016-09-06 18:41:24 +02:00
@windows
Scenario: Running :spawn with userscript on Windows
When I open about:blank
And I run :spawn -u (testdata)/userscripts/open_current_url.bat
And I wait until about:blank is loaded
Then the following tabs should be open:
- about:blank
add newline at the end of the file
2016-09-08 23:13:00 +02:00
- about:blank (active)
Reference in New Issue Copy Permalink