ftpd 2.0.1 → 2.0.2

data/features/ftp_server/rmdir.feature

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

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

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

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

@@ -1,10 +0,0 @@
-# frozen_string_literal: true
-
-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

@@ -1,71 +0,0 @@
-# frozen_string_literal: true
-
-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
-
-Given /^the test server has a NAT IP of (\S+)$/ do |s|
-  server.nat_ip = s
-end

data/features/ftp_server/structure_mount.feature

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

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

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

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

data/features/ftp_server/type.feature

@@ -1,59 +0,0 @@
-Feature: Representation Type
-
-  As a client
-  I want to set the representation type
-  So that I can interoperate with foreign operating systems
-
-  Background:
-    Given the test server is started
-
-  Scenario: ASCII/default
-    Given a successful login
-    Then the client successfully sets type "A"
-
-  Scenario: ASCII/Non-print
-    Given a successful login
-    Then the client successfully sets type "A N"
-
-  Scenario: ASCII/Telnet
-    Given a successful login
-    When the client successfully sets type "A T"
-
-  Scenario: Type IMAGE
-    Given a successful login
-    Then the client successfully sets type "I"
-
-  Scenario: Type EBCDIC
-    Given a successful login
-    When the client sets type "E"
-    Then the server returns a type not implemented error
-
-  Scenario: Type Local
-    Given a successful login
-    When the client sets type "L 7"
-    Then the server returns a type not implemented error
-
-  Scenario: Invalid Type
-    Given a successful login
-    When the client sets type "*"
-    Then the server returns an invalid type error
-
-  Scenario: Format Carriage Control
-    Given a successful login
-    When the client sets type "A C"
-    Then the server returns a type not implemented error
-
-  Scenario: Invalid Format
-    Given a successful login
-    When the client sets type "A *"
-    Then the server returns an invalid type error
-
-  Scenario: Not logged in
-    Given a successful connection
-    When the client sets type "S"
-    Then the server returns a not logged in error
-
-  Scenario: Missing parameter
-    Given a successful login
-    When the client sets type with no parameter
-    Then the server returns a syntax error

data/features/step_definitions/append.rb

@@ -1,17 +0,0 @@
-# frozen_string_literal: true
-
-When /^the client appends (.*)$/ do |args|
-  capture_error do
-    step "the client successfully appends #{args}"
-  end
-end
-
-When /^the client successfully appends text "(.*?)" onto "(.*?)"$/ do
-|local_path, remote_path|
-  client.append_text local_path, remote_path
-end
-
-When /^the client successfully appends binary "(.*?)" onto "(.*?)"$/ do
-|local_path, remote_path|
-  client.append_binary local_path, remote_path
-end

data/features/step_definitions/client.rb

@@ -1,27 +0,0 @@
-# frozen_string_literal: true
-
-require 'singleton'
-
-class Clients
-
-  include Singleton
-
-  def initialize
-    @clients = {}
-  end
-
-  def [](client_name)
-    @clients[client_name] ||= TestClient.new
-  end
-
-  def close
-    @clients.values.each(&:close)
-  end
-
-end
-
-def client(client_name = nil)
-  client_name ||= 'client'
-  client_name = client_name.strip
-  Clients.instance[client_name]
-end