investtools-ftpd 1.0.1

data/features/ftp_server/mkdir.feature

@@ -0,0 +1,70 @@
+Feature: Make directory
+
+  As a client
+  I want to create a directory
+  So that I can categorize my uploads
+
+  Background:
+    Given the test server is started
+
+  Scenario: Make directory
+    Given a successful login
+    When the client successfully makes directory "foo"
+    Then the server has directory "foo"
+
+  Scenario: Directory of a directory
+    Given a successful login
+    And the server has directory "foo"
+    When the client successfully makes directory "foo/bar"
+    Then the server has directory "foo/bar"
+
+  Scenario: After cwd
+    Given a successful login
+    And the server has directory "foo"
+    And the client successfully cd's to "foo"
+    When the client successfully makes directory "bar"
+    Then the server has directory "foo/bar"
+
+  Scenario: XMKD
+    Given a successful login
+    When the client successfully sends "XMKD foo"
+    Then the server has directory "foo"
+
+  Scenario: Missing directory
+    Given a successful login
+    When the client makes directory "foo/bar"
+    Then the server returns a not found error
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client makes directory "foo"
+    Then the server returns a not logged in error
+
+  Scenario: Already exists
+    Given a successful login
+    And the server has directory "foo"
+    When the client makes directory "foo"
+    Then the server returns an already exists error
+
+  Scenario: Directory of a file
+    Given a successful login
+    And the server has file "foo"
+    When the client makes directory "foo/bar"
+    Then the server returns a not a directory error
+
+  Scenario: Mkdir not enabled
+    Given the test server lacks mkdir
+    And a successful login
+    When the client makes directory "foo"
+    Then the server returns an unimplemented command error
+
+  Scenario: Missing path
+    Given a successful login
+    When the client sends "MKD"
+    Then the server returns a syntax error
+
+  Scenario: Access denied
+    Given a successful login
+    When the client makes directory "forbidden"
+    Then the server returns an access denied error
+

data/features/ftp_server/mode.feature

@@ -0,0 +1,43 @@
+Feature: Mode
+
+  As a client
+  I want to set the file transfer mode
+  So that can optimize the transfer
+
+  Background:
+    Given the test server is started
+
+  Scenario: Stream
+    Given a successful login
+    And the server has file "ascii_unix"
+    When the client successfully sets mode "S"
+    And the client successfully gets text "ascii_unix"
+    Then the remote file "ascii_unix" should match the local file
+
+  Scenario: Block
+    Given a successful login
+    And the server has file "ascii_unix"
+    When the client sets mode "B"
+    Then the server returns a mode not implemented error
+
+  Scenario: Compressed
+    Given a successful login
+    And the server has file "ascii_unix"
+    When the client sets mode "C"
+    Then the server returns a mode not implemented error
+
+  Scenario: Invalid
+    Given a successful login
+    And the server has file "ascii_unix"
+    When the client sets mode "*"
+    Then the server returns an invalid mode error
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client sets mode "S"
+    Then the server returns a not logged in error
+
+  Scenario: Missing parameter
+    Given a successful login
+    When the client sets mode with no parameter
+    Then the server returns a syntax error

data/features/ftp_server/name_list.feature

@@ -0,0 +1,77 @@
+Feature: Name List
+
+  As a client
+  I want to list file names
+  So that I can see what file to transfer
+
+  Background:
+    Given the test server is started
+
+  Scenario: Implicit
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    When the client successfully name-lists the directory
+    Then the file list should be in short form
+    And the file list should contain "foo"
+    And the file list should contain "bar"
+
+  Scenario: Root
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    When the client successfully name-lists the directory "/"
+    Then the file list should be in short form
+    And the file list should contain "foo"
+    And the file list should contain "bar"
+
+  Scenario: Parent of root
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    When the client successfully name-lists the directory "/.."
+    Then the file list should be in short form
+    And the file list should contain "foo"
+    And the file list should contain "bar"
+
+  Scenario: Subdir
+    Given a successful login
+    And the server has file "subdir/foo"
+    When the client successfully name-lists the directory "subdir"
+    Then the file list should be in short form
+    And the file list should contain "foo"
+
+  Scenario: '-a'
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    When the client successfully name-lists the directory "-a"
+    Then the file list should be in short form
+    And the file list should contain "foo"
+    And the file list should contain "bar"
+
+  Scenario: Passive
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    And the client is in passive mode
+    When the client successfully name-lists the directory
+    Then the file list should be in short form
+    And the file list should contain "foo"
+    And the file list should contain "bar"
+
+  Scenario: Missing directory
+    Given a successful login
+    When the client successfully name-lists the directory "missing/file"
+    Then the file list should be empty
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client name-lists the directory
+    Then the server returns a not logged in error
+
+  Scenario: List not enabled
+    Given the test server lacks list
+    And a successful login
+    When the client name-lists the directory
+    Then the server returns an unimplemented command error

data/features/ftp_server/name_list_tls.feature

@@ -0,0 +1,30 @@
+Feature: Name List TLS
+
+  As a client
+  I want to securely list file names
+  So that I can see what file to transfer
+  And nobody else can
+
+  Background:
+    Given the test server has TLS mode "explicit"
+    And the test server is started
+
+  Scenario: Active
+    Given a successful login with explicit TLS
+    And the server has file "foo"
+    And the server has file "bar"
+    And the client is in active mode
+    When the client successfully name-lists the directory
+    Then the file list should be in short form
+    And the file list should contain "foo"
+    And the file list should contain "bar"
+
+  Scenario: Passive
+    Given a successful login with explicit TLS
+    And the server has file "foo"
+    And the server has file "bar"
+    And the client is in passive mode
+    When the client successfully name-lists the directory
+    Then the file list should be in short form
+    And the file list should contain "foo"
+    And the file list should contain "bar"

data/features/ftp_server/noop.feature

@@ -0,0 +1,17 @@
+Feature: No Operation
+
+  As a client
+  I want to keep the connection alive
+  So that I don't have to log in so often
+
+  Background:
+    Given the test server is started
+
+  Scenario: NOP
+    Given a successful connection
+    Then the client successfully does nothing
+
+  Scenario: With a parameter
+    Given a successful connection
+    When the client does nothing with a parameter
+    Then the server returns a syntax error

data/features/ftp_server/options.feature

@@ -0,0 +1,17 @@
+Feature: Options
+
+  As a client
+  I want to know set options
+  To tailor the server's behavior
+
+  Background:
+    Given the test server is started
+    And the client connects
+
+  Scenario: No argument
+    When the client sends "OPTS"
+    Then the server returns a syntax error
+
+  Scenario: Unknown option command
+    When the client sets option "ABC"
+    Then the server returns a bad option error

data/features/ftp_server/pasv.feature

@@ -0,0 +1,23 @@
+Feature: PASV
+
+  As a programmer
+  I want good error messages
+  So that I can correct problems
+
+  Background:
+    Given the test server is started
+
+  Scenario: No argument
+    Given a successful login
+    Then the client successfully sends "PASV"
+
+  Scenario: After "EPSV ALL"
+    Given a successful login
+    Given the client successfully sends "EPSV ALL"
+    When the client sends "PASV"
+    Then the server sends a not allowed after epsv all error
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client sends "EPSV"
+    Then the server returns a not logged in error

data/features/ftp_server/port.feature

@@ -0,0 +1,49 @@
+Feature: PORT
+
+  As a programmer
+  I want good error messages
+  So that I can correct problems
+
+  Background:
+    Given the test server is started
+
+  Scenario: Port 1024
+    Given a successful login
+    Then the client successfully sends "PORT 1,2,3,4,4,0"
+
+  Scenario: Port 1023; low ports disallowed
+    Given the test server disallows low data ports
+    And a successful login
+    When the client sends "PORT 1,2,3,4,3,255"
+    Then the server returns an unimplemented parameter error
+
+  Scenario: Port 1023; low ports allowed
+    Given the test server allows low data ports
+    And a successful login
+    Then the client successfully sends "PORT 1,2,3,4,3,255"
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client sends PORT "1,2,3,4,5,6"
+    Then the server returns a not logged in error
+
+  Scenario: Incorrect number of bytes
+    Given a successful login
+    When the client sends PORT "1,2,3,4,5"
+    Then the server returns a syntax error
+
+  Scenario: Ill formatted byte
+    Given a successful login
+    When the client sends PORT "1,2,3,4,5,0006"
+    Then the server returns a syntax error
+
+  Scenario: Byte out of range
+    Given a successful login
+    When the client sends PORT "1,2,3,4,5,256"
+    Then the server returns a syntax error
+
+  Scenario: After "EPSV ALL"
+    Given a successful login
+    Given the client successfully sends "EPSV ALL"
+    When the client sends "PORT 1,2,3,4,4,0"
+    Then the server sends a not allowed after epsv all error

data/features/ftp_server/put.feature

@@ -0,0 +1,79 @@
+Feature: Put
+
+  As a client
+  I want to upload a file
+  So that someone else can have it
+
+  Background:
+    Given the test server is started
+
+  Scenario: ASCII file with *nix line endings
+    Given a successful login
+    And the client has file "ascii_unix"
+    When the client successfully puts text "ascii_unix"
+    Then the remote file "ascii_unix" should match the local file
+    And the remote file "ascii_unix" should have unix line endings
+
+  Scenario: ASCII file with windows line endings
+    Given a successful login
+    And the client has file "ascii_windows"
+    When the client successfully puts text "ascii_windows"
+    Then the remote file "ascii_windows" should match the local file
+    And the remote file "ascii_windows" should have unix line endings
+
+  Scenario: Binary file
+    Given a successful login
+    And the client has file "binary"
+    When the client successfully puts binary "binary"
+    Then the remote file "binary" should exactly match the local file
+
+  Scenario: Passive
+    Given a successful login
+    And the client has file "ascii_unix"
+    And the client is in passive mode
+    When the client successfully puts text "ascii_unix"
+    Then the remote file "ascii_unix" should match the local file
+
+  Scenario: Non-root working directory
+    Given a successful login
+    And the client has file "ascii_unix"
+    And the server has directory "foo"
+    And the client successfully cd's to "foo"
+    When the client successfully puts text "ascii_unix"
+    Then the remote file "foo/ascii_unix" should match the local file
+
+  Scenario: Access denied
+    Given a successful login
+    And the client has file "forbidden"
+    When the client puts text "forbidden"
+    Then the server returns an access denied error
+
+  Scenario: Missing directory
+    Given a successful login
+    And the client has file "bar"
+    When the client puts text "foo/bar"
+    Then the server returns a not found error
+
+  Scenario: Not logged in
+    Given a successful connection
+    And the client has file "foo"
+    When the client puts text "foo"
+    Then the server returns a not logged in error
+
+  Scenario: Missing path
+    Given a successful login
+    When the client puts with no path
+    Then the server returns a syntax error
+
+  Scenario: File system error
+    Given a successful login
+    And the client has file "unable"
+    When the client puts text "unable"
+    Then the server returns an action not taken error
+
+  Scenario: Write not enabled
+    Given the test server lacks write
+    And a successful login
+    And the client has file "foo"
+    When the client puts text "foo"
+    Then the server returns an unimplemented command error

data/features/ftp_server/put_tls.feature

@@ -0,0 +1,23 @@
+Feature: Put TLS
+
+  As a client
+  I want to put a file securely
+  So that nobody can intercept it
+
+  Background:
+    Given the test server has TLS mode "explicit"
+    And the test server is started
+
+  Scenario: Active
+    Given a successful login with explicit TLS
+    And the client has file "ascii_unix"
+    And the client is in active mode
+    When the client successfully puts text "ascii_unix"
+    Then the remote file "ascii_unix" should match the local file
+
+  Scenario: Passive
+    Given a successful login with explicit TLS
+    And the client has file "ascii_unix"
+    And the client is in passive mode
+    When the client successfully puts text "ascii_unix"
+    Then the remote file "ascii_unix" should match the local file

data/features/ftp_server/put_unique.feature

@@ -0,0 +1,56 @@
+Feature: Put Unique
+
+  As a client
+  I want to upload a file with a unique name
+  So that it will not overwrite an existing file
+
+  Background:
+    Given the test server is started
+
+  Scenario: File does not exist
+    Given a successful login
+    And the client has file "foo"
+    When the client successfully stores unique "foo"
+    Then the server should have a file with the contents of "foo"
+
+  Scenario: Suggest name
+    Given a successful login
+    And the client has file "foo"
+    When the client successfully stores unique "foo" to "bar"
+    Then the server should have a file with the contents of "foo"
+    And the server should have 1 file with "bar" in the name
+
+  Scenario: Suggested name exists
+    Given a successful login
+    And the client has file "foo"
+    And the server has file "bar"
+    When the client successfully stores unique "foo" to "bar"
+    Then the server should have a file with the contents of "foo"
+    Then the server should have a file with the contents of "bar"
+    And the server should have 2 files with "bar" in the name
+
+  Scenario: Non-root working directory
+    Given a successful login
+    And the client has file "bar"
+    And the server has directory "foo"
+    And the client successfully cd's to "foo"
+    When the client successfully stores unique "bar" to "bar"
+    Then the remote file "foo/bar" should match the local file
+
+  Scenario: Missing directory
+    Given a successful login
+    And the client has file "bar"
+    When the client stores unique "bar" to "foo/bar"
+    Then the server returns a not found error
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client sends "STOU"
+    Then the server returns a not logged in error
+
+  Scenario: Write not enabled
+    Given the test server lacks write
+    And a successful login
+    And the client has file "foo"
+    When the client stores unique "foo"
+    Then the server returns an unimplemented command error