investtools-ftpd 1.0.1

data/features/ftp_server/quit.feature

@@ -0,0 +1,23 @@
+Feature: Quit
+
+  As a client
+  In order to free up resources
+  I want to close the connection
+
+  Background:
+    Given the test server is started
+
+  Scenario: Logged in
+    Given a successful login
+    When the client successfully quits
+    Then the client should not be logged in
+
+  Scenario: With a parameter
+    Given a successful connection
+    When the client quits with a parameter
+    Then the server returns a syntax error
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client quits
+    Then the server returns a not logged in error

data/features/ftp_server/reinitialize.feature

@@ -0,0 +1,13 @@
+Feature: Reinitialize
+
+  As a client
+  I want to know this command is not supported
+  So that I can avoid using it
+
+  Background:
+    Given the test server is started
+
+  Scenario: Unimplemented
+    Given a successful connection
+    When the client sends command "REIN"
+    Then the server returns an unimplemented command error

data/features/ftp_server/rename.feature

@@ -0,0 +1,97 @@
+Feature: Rename
+
+  As a client
+  I want to rename a file
+  To correct an improper name
+
+  Background:
+    Given the test server is started
+
+  Scenario: Rename
+    Given a successful login
+    And the server has file "foo"
+    When the client successfully renames "foo" to "bar"
+    Then the server should not have file "foo"
+    And the server should have file "bar"
+
+  Scenario: Move
+    Given a successful login
+    And the server has file "foo/bar"
+    And the server has directory "baz"
+    When the client successfully renames "foo/bar" to "baz/qux"
+    Then the server should not have file "foo/bar"
+    And the server should have file "baz/qux"
+
+  Scenario: Non-root working directory
+    Given a successful login
+    And the server has file "foo/bar"
+    And the client successfully cd's to "foo"
+    When the client successfully renames "bar" to "baz"
+    Then the server should not have file "foo/bar"
+    Then the server should have file "foo/baz"
+
+  Scenario: Access denied (source)
+    Given a successful login
+    When the client renames "forbidden" to "foo"
+    Then the server returns an access denied error
+
+  Scenario: Access denied (destination)
+    Given a successful login
+    And the server has file "foo"
+    When the client renames "foo" to "forbidden"
+    Then the server returns an access denied error
+
+  Scenario: Source missing
+    Given a successful login
+    When the client renames "foo" to "bar"
+    Then the server returns a not found error
+
+  Scenario: Destination exists
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    When the client renames "foo" to "bar"
+    Then the server returns an already exists error
+
+  Scenario: Not logged in (RNFR)
+    Given a successful connection
+    When the client sends "RNFR foo"
+    Then the server returns a not logged in error
+
+  Scenario: Not logged in (RNTO)
+    Given a successful connection
+    When the client sends "RNTO foo"
+    # Although the RNTO command checks for logged in, sequence error
+    # gets triggered first.
+    Then the server returns a bad sequence error
+
+  Scenario: Missing path (RNFR)
+    Given a successful login
+    When the client sends "RNFR"
+    Then the server returns a syntax error
+
+  Scenario: Missing path (RNTO)
+    Given a successful login
+    And the server has file "foo"
+    And the client successfully sends "RNFR foo"
+    When the client sends "RNTO"
+    Then the server returns a syntax error
+
+  Scenario: Rename not enabled
+    Given the test server lacks rename
+    And a successful login
+    And the server has file "foo"
+    When the client renames "foo" to "bar"
+    Then the server returns an unimplemented command error
+
+  Scenario: RNTO without RNFR
+    Given a successful login
+    When the client sends "RNTO bar"
+    Then the server returns a bad sequence error
+
+  Scenario: RNFR not followed by RNTO
+    Given a successful login
+    And the server has file "foo"
+    And the client sends "RNFR foo"
+    When the client sends "NOOP"
+    Then the server returns a bad sequence error

data/features/ftp_server/rmdir.feature

@@ -0,0 +1,71 @@
+Feature: Remove directory
+
+  As a client
+  I want to remove a directory
+  To reduce clutter
+
+  Background:
+    Given the test server is started
+
+  Scenario: Make directory
+    Given a successful login
+    And the server has directory "foo"
+    When the client successfully removes directory "foo"
+    Then the server should not have directory "foo"
+
+  Scenario: Directory of a directory
+    Given a successful login
+    And the server has directory "foo/bar"
+    When the client successfully removes directory "foo/bar"
+    Then the server should not have directory "foo/bar"
+    And the server has directory "foo"
+
+  Scenario: After cwd
+    Given a successful login
+    And the server has directory "foo/bar"
+    And the client successfully cd's to "foo"
+    When the client successfully removes directory "bar"
+    Then the server should not have directory "foo/bar"
+
+  Scenario: XRMD
+    Given a successful login
+    And the server has directory "foo"
+    When the client successfully sends "XRMD foo"
+    Then the server should not have directory "foo"
+
+  Scenario: Missing directory
+    Given a successful login
+    When the client removes directory "foo/bar"
+    Then the server returns a not found error
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client removes directory "foo"
+    Then the server returns a not logged in error
+
+  Scenario: Does not exist
+    Given a successful login
+    When the client removes directory "foo"
+    Then the server returns a not found error
+
+  Scenario: Remove a file
+    Given a successful login
+    And the server has file "foo"
+    When the client removes directory "foo"
+    Then the server returns a not a directory error
+
+  Scenario: Rmdir not enabled
+    Given the test server lacks rmdir
+    And a successful login
+    When the client removes directory "foo"
+    Then the server returns an unimplemented command error
+
+  Scenario: Missing path
+    Given a successful login
+    When the client sends "RMD"
+    Then the server returns a syntax error
+
+  Scenario: Access denied
+    Given a successful login
+    When the client removes directory "forbidden"
+    Then the server returns an access denied error

data/features/ftp_server/site.feature

@@ -0,0 +1,13 @@
+Feature: Site
+
+  As a client
+  I want to know this command is not supported
+  So that I can avoid using it
+
+  Background:
+    Given the test server is started
+
+  Scenario: Unimplemented
+    Given a successful connection
+    When the client sends command "SITE"
+    Then the server returns an unimplemented command error

data/features/ftp_server/size.feature

@@ -0,0 +1,69 @@
+Feature: Size
+
+  As a client
+  I want to know the size of a file
+  So that I can tell how long it will take to get it
+
+  Background:
+    Given the test server is started
+
+  Scenario: ASCII file with *nix line endings
+    Given a successful login
+    And the server has file "ascii_unix"
+    When the client successfully gets size of text "ascii_unix"
+    Then the reported size should be "83"
+
+  Scenario: ASCII file with windows line endings
+    Given a successful login
+    And the server has file "ascii_windows"
+    When the client successfully gets size of text "ascii_windows"
+    Then the reported size should be "83"
+
+  Scenario: Binary file
+    Given a successful login
+    And the server has file "binary"
+    When the client successfully gets size of binary "binary"
+    Then the reported size should be "256"
+
+  Scenario: File in subdirectory
+    Given a successful login
+    And the server has file "foo/ascii_unix"
+    Then the client successfully gets size of text "foo/ascii_unix"
+
+  Scenario: Non-root working directory
+    Given a successful login
+    And the server has file "foo/ascii_unix"
+    And the client successfully cd's to "foo"
+    Then the client successfully gets size of text "ascii_unix"
+
+  Scenario: Access denied
+    Given a successful login
+    When the client gets size of text "forbidden"
+    Then the server returns an access denied error
+
+  Scenario: Missing file
+    Given a successful login
+    When the client gets size of text "foo"
+    Then the server returns a not found error
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client gets size of text "foo"
+    Then the server returns a not logged in error
+
+  Scenario: Missing path
+    Given a successful login
+    When the client gets size with no path
+    Then the server returns a syntax error
+
+  Scenario: File system error
+    Given a successful login
+    When the client gets size of text "unable"
+    Then the server returns an action not taken error
+
+  Scenario: Read not enabled
+    Given the test server lacks read
+    And a successful login
+    And the server has file "foo"
+    When the client gets size of text "foo"
+    Then the server returns an unimplemented command error

data/features/ftp_server/status.feature

@@ -0,0 +1,18 @@
+Feature: Status
+
+  As a client
+  I want server status
+  To know what state the server is in
+
+  Background:
+    Given the test server is started
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client requests status
+    Then the server returns a not logged in error
+
+  Scenario: Server status
+    Given a successful login
+    When the client successfully requests status
+    Then the server returns its title

data/features/ftp_server/step_definitions/logging.rb

@@ -0,0 +1,8 @@
+Then /^the server should have written( no)? log output$/ do |neg|
+  verb = if neg
+           :to
+         else
+           :to_not
+         end
+  expect(server.log_output).send(verb, eq(''))
+end

data/features/ftp_server/step_definitions/test_server.rb

@@ -0,0 +1,65 @@
+def server
+  @server ||= TestServer.new
+end
+
+Given /^the test server is started$/ do
+  server.start
+end
+
+Given /^the test server has TLS mode "(\w+)"$/ do |mode|
+  server.tls = mode.to_sym
+end
+
+Given(/^the test server is bound to "(.*?)"$/) do |ip_address|
+  server.interface = ip_address
+end
+
+Given /^the test server has logging (enabled|disabled)$/ do |state|
+  server.logging = state == 'enabled'
+end
+
+Given /^the test server lacks (\w+)$/ do |feature|
+  server.send "#{feature}=", false
+end
+
+Given /^the test server has auth level "(.*?)"$/ do |auth_level|
+  auth_level = Ftpd.const_get(auth_level)
+  server.auth_level = auth_level
+end
+
+Given /^the test server has session timeout set to (\S+) seconds$/ do
+|timeout|
+  server.session_timeout = timeout.to_f
+end
+
+Given /^the test server has session timeout disabled$/ do
+  server.session_timeout = nil
+end
+
+Given /^the test server disallows low data ports$/ do
+  server.allow_low_data_ports = false
+end
+
+Given /^the test server allows low data ports$/ do
+  server.allow_low_data_ports = true
+end
+
+Given /^the test server has max_connections set to (\d+)$/ do |s|
+  server.max_connections = s.to_i
+end
+
+Given /^the test server has max_connections_per_ip set to (\d+)$/ do |s|
+  server.max_connections_per_ip = s.to_i
+end
+
+Given /^the test server has no max failed login attempts$/ do
+  server.max_failed_logins = nil
+end
+
+Given /^the test server has a max of (\d+) failed login attempts$/ do |s|
+  server.max_failed_logins = s.to_i
+end
+
+Given /^the test server has a failed login delay of (\S+) seconds$/ do |s|
+  server.failed_login_delay = s.to_f
+end

data/features/ftp_server/structure_mount.feature

@@ -0,0 +1,13 @@
+Feature: Structure Mount
+
+  As a client
+  I want to know this command is not supported
+  So that I can avoid using it
+
+  Background:
+    Given the test server is started
+
+  Scenario: Unimplemented
+    Given a successful connection
+    When the client sends command "SMNT"
+    Then the server returns an unimplemented command error

data/features/ftp_server/syntax_errors.feature

@@ -0,0 +1,18 @@
+Feature: Syntax Errors
+
+  As a client
+  I want good error messages
+  So that I can figure out what went wrong
+
+  Background:
+    Given the test server is started
+
+  Scenario: Empty command
+    Given a successful connection
+    When the client sends an empty command
+    Then the server returns a syntax error
+
+  Scenario: Command contains non-word characters
+    Given a successful connection
+    When the client sends a non-word command
+    Then the server returns a syntax error

data/features/ftp_server/syst.feature

@@ -0,0 +1,18 @@
+Feature: Port
+
+  As a client
+  I want to identify the server
+  So that I know how it will behave
+
+  Background:
+    Given the test server is started
+
+  Scenario: Success
+    Given a successful connection
+    When the client successfully queries system ID
+    Then the server returns a system ID reply
+
+  Scenario: With argument
+    Given a successful login
+    When the client sends "SYST 1"
+    Then the server returns a syntax error

data/features/ftp_server/timeout.feature

@@ -0,0 +1,26 @@
+Feature: Port
+
+  As a programmer
+  I want idle sessions to timeout and disconnect
+  So that I can claim RFC compliance
+
+  Scenario: Session idle too long
+    Given the test server has session timeout set to 0.5 seconds
+    And the test server is started
+    And a successful login
+    When the client is idle for 0.6 seconds
+    Then the client should not be connected
+
+  Scenario: Session not idle too long
+    Given the test server has session timeout set to 0.5 seconds
+    And the test server is started
+    And a successful login
+    When the client is idle for 0 seconds
+    Then the client should be connected
+
+  Scenario: Timeout disabled
+    Given the test server has session timeout disabled
+    And the test server is started
+    And a successful login
+    When the client is idle for 0.6 seconds
+    Then the client should be connected