qutebrowser/tests/integration/features/spawn.feature
Philipp Hansch c016c77da4 Try to fix Windows path issue with new custom step
On windows, using '/' in pathnames won't work, so it's impossible to use
to describe a path in a feature spec. The solution is to move the path
logic out of the feature spec and hand it over to `os.path.join` in a
new custom step for userscripts.
2016-03-29 01:37:40 +02:00

25 lines
987 B
Gherkin

Feature: :spawn
Scenario: Running :spawn
When I run :spawn -v echo "Hello"
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
Scenario: Running :spawn with invalid quoting
When I run :spawn ""'""
Then the error "Error while splitting command: No closing quotation" should be shown
Scenario: Running :spawn with url variable
When I run :spawn echo {url}
Then "Executing echo with args ['about:blank'], userscript=False" should be logged
Scenario: Running :spawn with userscript
When I execute the userscript open_current_url
And I wait until about:blank is loaded
Then the following tabs should be open:
- about:blank
- about:blank (active)