investtools-ftpd 1.0.1

data/features/ftp_server/get_tls.feature

@@ -0,0 +1,23 @@
+Feature: Get TLS
+
+  As a client
+  I want to get a file
+  So that I have it on my computer
+
+  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 "ascii_unix"
+    And the client is in active mode
+    When the client successfully gets text "ascii_unix"
+    Then the local file "ascii_unix" should match the remote file
+
+  Scenario: Passive
+    Given a successful login with explicit TLS
+    And the server has file "ascii_unix"
+    And the client is in passive mode
+    When the client successfully gets text "ascii_unix"
+    Then the local file "ascii_unix" should match the remote file

data/features/ftp_server/help.feature

@@ -0,0 +1,21 @@
+Feature: Help
+
+  As a client
+  I want to ask for help
+  So that I can know which commands are supported
+
+  Background:
+    Given the test server is started
+    And a successful connection
+
+  Scenario: No argument
+    When the client successfully asks for help
+    Then the server should return a list of commands
+
+  Scenario: Known command
+    When the client successfully asks for help for "NOOP"
+    Then the server should return help for "NOOP"
+
+  Scenario: Unknown command
+    When the client successfully asks for help for "FOO"
+    Then the server should return no help for "FOO"

data/features/ftp_server/implicit_tls.feature

@@ -0,0 +1,23 @@
+Feature: Implicit TLS
+
+  As a server
+  I want to use implicit TLS
+  Because I must serve out-of-date clients
+
+  Background:
+    Given the test server has TLS mode "implicit"
+    And the test server is started
+
+  Scenario: Active
+    Given a successful login with implicit 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 implicit 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/invertability.feature

@@ -0,0 +1,15 @@
+Feature: Get
+
+  As a client
+  I want a file to be the same when I get it as it was when I put it
+  So that I can use the FTP server for storage
+
+  Background:
+    Given the test server is started
+
+  Scenario: Binary file
+    Given a successful login
+    And the client has file "binary"
+    When the client successfully puts binary "binary"
+    And the client successfully gets binary "binary"
+    Then the local file "binary" should match its template

data/features/ftp_server/list.feature

@@ -0,0 +1,94 @@
+Feature: List
+
+  As a client
+  I want to list files
+  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 lists the directory
+    Then the file list should be in long 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 lists the directory "/"
+    Then the file list should be in long 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 lists the directory "/.."
+    Then the file list should be in long 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 lists the directory "subdir"
+    Then the file list should be in long form
+    And the file list should contain "foo"
+
+  Scenario: After CWD
+    Given a successful login
+    And the server has file "subdir/foo"
+    And the client successfully cd's to "subdir"
+    When the client successfully lists the directory
+    Then the file list should be in long form
+    And the file list should contain "foo"
+
+  Scenario: Glob
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    When the client successfully lists the directory "f*"
+    Then the file list should be in long form
+    And the file list should contain "foo"
+    And the file list should not 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 lists the directory
+    Then the file list should be in long form
+    And the file list should contain "foo"
+    And the file list should contain "bar"
+
+  Scenario: -a
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    When the client successfully lists the directory "-a"
+    Then the file list should be in long 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 lists the directory "missing/file"
+    Then the file list should be empty
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client 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 lists the directory
+    Then the server returns an unimplemented command error

data/features/ftp_server/list_tls.feature

@@ -0,0 +1,29 @@
+Feature: List TLS
+
+  As a client
+  I want to list files
+  So that I can see what file to transfer
+
+  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 lists the directory
+    Then the file list should be in long 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 lists the directory
+    Then the file list should be in long form
+    And the file list should contain "foo"
+    And the file list should contain "bar"

data/features/ftp_server/logging.feature

@@ -0,0 +1,11 @@
+Feature: Logging
+
+  As a programmer
+  I want to see logging output
+  So that I can fix FTP protocol problems
+
+  Scenario: Logging enabled
+    Given the test server has logging enabled
+    And the test server is started
+    And a successful login
+    Then the server should have written log output

data/features/ftp_server/login_auth_level_account.feature

@@ -0,0 +1,51 @@
+Feature: Login
+
+  As a client
+  I want to log in
+  So that I can transfer files
+
+  Background:
+    Given the test server has auth level "AUTH_ACCOUNT"
+    And the test server is started
+
+  Scenario: Normal connection
+    Given a successful login
+    Then the server returns no error
+    And the client should be logged in
+
+  Scenario: Bad user
+    Given the client connects
+    When the client logs in with bad user
+    Then the server returns a login incorrect error
+    And the client should not be logged in
+
+  Scenario: Bad password
+    Given a successful connection
+    When the client logs in with bad password
+    Then the server returns a login incorrect error
+    And the client should not be logged in
+
+  Scenario: Bad account
+    Given a successful connection
+    When the client logs in with bad account
+    Then the server returns a login incorrect error
+    And the client should not be logged in
+
+  Scenario: ACCT without parameter
+    Given a successful connection
+    And the client sends a user
+    And the client sends a password
+    When the client sends "ACCT"
+    Then the server returns a syntax error
+
+  Scenario: PASS not followed by ACCT
+    Given a successful connection
+    And the client sends a user
+    And the client sends a password
+    When the client sends "NOOP"
+    Then the server returns a bad sequence error
+
+  Scenario: ACCT out of sequence
+    Given a successful connection
+    When the client sends "ACCT"
+    Then the server returns a bad sequence error

data/features/ftp_server/login_auth_level_password.feature

@@ -0,0 +1,59 @@
+Feature: Login
+
+  As a client
+  I want to log in
+  So that I can transfer files
+
+  Background:
+    Given the test server has auth level "AUTH_PASSWORD"
+    And the test server is started
+
+  Scenario: Normal connection
+    Given a successful login
+    Then the server returns no error
+    And the client should be logged in
+
+  Scenario: Bad user
+    Given the client connects
+    When the client logs in with bad user
+    Then the server returns a login incorrect error
+    And the client should not be logged in
+
+  Scenario: Bad password
+    Given a successful connection
+    When the client logs in with bad password
+    Then the server returns a login incorrect error
+    And the client should not be logged in
+
+  Scenario: Already logged in
+    Given a successful login
+    When the client logs in
+    Then the server returns a bad sequence error
+    And the client should be logged in
+
+  Scenario: PASS when already logged in
+    Given a successful login
+    When the client sends a password
+    Then the server returns a bad sequence error
+
+  Scenario: PASS after failed login
+    Given a failed login
+    When the client sends a password
+    Then the server returns a bad sequence error
+
+  Scenario: PASS without USER
+    Given a successful connection
+    And the client sends a password
+    Then the server returns a bad sequence error
+
+  Scenario: PASS without parameter
+    Given a successful connection
+    And the client sends a user
+    When the client sends a password with no parameter
+    Then the server returns a syntax error
+
+  Scenario: USER not followed by PASS
+    Given a successful connection
+    And the client sends a user
+    When the client sends "NOOP"
+    Then the server returns a bad sequence error

data/features/ftp_server/login_auth_level_user.feature

@@ -0,0 +1,31 @@
+Feature: Login
+
+  As a client
+  I want to log in
+  So that I can transfer files
+
+  Background:
+    Given the test server has auth level "AUTH_USER"
+    And the test server is started
+
+  Scenario: Normal connection
+    Given a successful login
+    Then the server returns no error
+    And the client should be logged in
+
+  Scenario: Bad user
+    Given the client connects
+    When the client logs in with bad user
+    Then the server returns a login incorrect error
+    And the client should not be logged in
+
+  Scenario: Already logged in
+    Given a successful login
+    When the client logs in
+    Then the server returns a bad sequence error
+    And the client should be logged in
+
+  Scenario: USER without parameter
+    Given a successful connection
+    And the client sends a user with no parameter
+    Then the server returns a syntax error

data/features/ftp_server/max_connections.feature

@@ -0,0 +1,39 @@
+Feature: Max Connections
+
+  As an administrator
+  I want to limit the number of connections
+  To prevent overload
+
+  Scenario: Total connections
+    Given the test server has max_connections set to 2
+    And the test server is started
+    And the 1st client connects
+    And the 2nd client connects
+    When the 3rd client tries to connect
+    Then the server returns a too many connections error
+
+  Scenario: Connections per user
+    And the test server has max_connections_per_ip set to 1
+    And the test server is started
+    And the 1st client connects from 127.0.0.1
+    And the 2nd client connects from 127.0.0.2
+    When the 3rd client tries to connect from 127.0.0.2
+    Then the server returns a too many connections error
+
+  Scenario: TLS
+    Given the test server has max_connections set to 2
+    And the test server has TLS mode "explicit"
+    And the test server is started
+    And the 1st client connects
+    And the 2nd client connects
+    When the 3rd client tries to connect
+    Then the server returns a too many connections error
+
+  Scenario: Connections per user, TLS
+    And the test server has max_connections_per_ip set to 1
+    And the test server has TLS mode "explicit"
+    And the test server is started
+    And the 1st client connects from 127.0.0.1
+    And the 2nd client connects from 127.0.0.2
+    When the 3rd client tries to connect from 127.0.0.2
+    Then the server returns a too many connections error

data/features/ftp_server/mdtm.feature

@@ -0,0 +1,53 @@
+Feature: MDTM
+
+  As a client
+  I want to get a file's modification time
+  So that I can detect when it changes
+
+  Background:
+    Given the test server is started
+
+  Scenario: File in current directory
+    Given a successful login
+    And the server has file "ascii_unix"
+    And the file "ascii_unix" has mtime "2014-01-02 13:14:15.123456"
+    When the client successfully gets mtime of "ascii_unix"
+    Then the reported mtime should be "20140102131415"
+
+  Scenario: File in subdirectory
+    Given a successful login
+    And the server has file "foo/ascii_unix"
+    Then the client successfully gets mtime of "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 mtime of "ascii_unix"
+
+  Scenario: Access denied
+    Given a successful login
+    When the client gets mtime of "forbidden"
+    Then the server returns an access denied error
+
+  Scenario: Missing file
+    Given a successful login
+    When the client gets mtime of "foo"
+    Then the server returns a not found error
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client gets mtime of "foo"
+    Then the server returns a not logged in error
+
+  Scenario: Missing path
+    Given a successful login
+    When the client gets mtime with no path
+    Then the server returns a syntax error
+
+  Scenario: List not enabled
+    Given the test server lacks list
+    And a successful login
+    And the server has file "foo"
+    When the client gets mtime of "foo"
+    Then the server returns an unimplemented command error