ftpd 2.0.1 → 2.0.2

data/features/ftp_server/list_tls.feature

@@ -1,29 +0,0 @@
-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

@@ -1,11 +0,0 @@
-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

@@ -1,51 +0,0 @@
-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

@@ -1,59 +0,0 @@
-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

@@ -1,31 +0,0 @@
-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

@@ -1,39 +0,0 @@
-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

@@ -1,53 +0,0 @@
-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

data/features/ftp_server/mkdir.feature

@@ -1,70 +0,0 @@
-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

@@ -1,43 +0,0 @@
-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

@@ -1,77 +0,0 @@
-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