ftpd 0.0.0.pre1

data/features/mode.feature

@@ -0,0 +1,40 @@
+Feature: Mode
+
+  As a client
+  I want to set the file transfer mode
+  So that can optimize the transfer
+
+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/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
+
+  Scenario: List implicit
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    When the client 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: List root
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    When the client 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: List subdir
+    Given a successful login
+    And the server has file "subdir/foo"
+    When the client name lists the directory "subdir"
+    Then the file list should be in short form
+    And the file list should contain "foo"
+
+  Scenario: List glob
+    Given a successful login
+    And the server has file "foo"
+    And the server has file "bar"
+    When the client name lists the directory "f*"
+    Then the file list should be in short 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 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: TLS
+    pending "TLS not supported in active mode (see README)"
+
+  Scenario: TLS, Passive
+    Given a successful login with TLS
+    And the server has file "foo"
+    And the server has file "bar"
+    And the client is in passive mode
+    When the client 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: Path outside tree
+    Given a successful login
+    When the client name lists the directory ".."
+    Then the server returns an access denied error
+
+  Scenario: Missing file
+    Given a successful login
+    When the client name lists the directory "missing/file"
+    Then the server returns a no such file error
+
+  Scenario: Not logged in
+    Given a successful connection
+    When the client name lists the directory
+    Then the server returns a not logged in error

data/features/noop.feature

@@ -0,0 +1,14 @@
+Feature: No Operation
+
+  As a client
+  I want to keep the connection alive
+  So that I don't have to log in so often
+
+  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/port.feature

@@ -0,0 +1,25 @@
+Feature: Port
+
+  As a programmer
+  I want good error messages
+  So that I can correct problems
+
+  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

data/features/put.feature

@@ -0,0 +1,65 @@
+Feature: Put
+
+  As a client
+  I want to put a file
+  So that someone else can have it
+
+  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: TLS
+    pending "TLS not supported in active mode (see README)"
+
+  Scenario: TLS, Passive
+    Given a successful login with 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
+
+  Scenario: Path outside tree
+    Given a successful login
+    And the client has file "foo"
+    When the client puts text "../foo"
+    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 no such file 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

data/features/quit.feature

@@ -0,0 +1,20 @@
+Feature: Quit
+
+  As a client
+  In order to free up resources
+  I want to close the connection
+
+  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/step_definitions/client_and_server_files.rb

@@ -0,0 +1,24 @@
+def unix_line_endings(exactly, s)
+  return s if exactly
+  s.gsub(/\r\n/, "\n")
+end
+
+Then /^the remote file "(.*?)" should( exactly)? match the local file$/ do
+|remote_path, exactly|
+  local_path = File.basename(remote_path)
+  remote_contents = @server.file_contents(remote_path)
+  local_contents = @client.file_contents(local_path)
+  remote_contents = unix_line_endings(exactly, remote_contents)
+  local_contents = unix_line_endings(exactly, local_contents)
+  remote_contents.should == local_contents
+end
+
+Then /^the local file "(.*?)" should( exactly)? match the remote file$/ do
+|local_path, exactly|
+  remote_path = local_path
+  remote_contents = @server.file_contents(remote_path)
+  local_contents = @client.file_contents(local_path)
+  remote_contents = unix_line_endings(exactly, remote_contents)
+  local_contents = unix_line_endings(exactly, local_contents)
+  local_contents.should == remote_contents
+end

data/features/step_definitions/client_files.rb

@@ -0,0 +1,9 @@
+Given /^the client has file "(.*?)"$/ do |local_path|
+  @client.add_file local_path
+end
+
+Then /^the local file "(.*?)" should have (unix|windows) line endings$/ do
+|local_path, line_ending_type|
+  line_ending_type(@client.file_contents(local_path)).should ==
+    line_ending_type.to_sym
+end

data/features/step_definitions/command.rb

@@ -0,0 +1,5 @@
+When /^the client sends command "(.*?)"$/ do |command|
+  capture_error do
+    @client.raw command
+  end
+end

data/features/step_definitions/connect.rb

@@ -0,0 +1,15 @@
+require 'double_bag_ftps'
+require 'net/ftp'
+
+When /^the client connects( with TLS)?$/ do |with_tls|
+  @client = TestClient.new(:tls => with_tls)
+  @client.connect(@server.host, @server.port)
+end
+
+Then /^the connection is closed$/ do
+  @client.should be_closed
+end
+
+Then /^the connection is open$/ do
+  @client.should be_open
+end

data/features/step_definitions/delete.rb

@@ -0,0 +1,15 @@
+When /^the client deletes "(.*?)"$/ do |path|
+  capture_error do
+    step %Q(the client successfully deletes "#{path}")
+  end
+end
+
+When /^the client successfully deletes "(.*?)"$/ do |path|
+  @client.delete path
+end
+
+When /^the client deletes with no path$/ do
+  capture_error do
+    @client.raw 'DELE'
+  end
+end

data/features/step_definitions/directories.rb

@@ -0,0 +1,22 @@
+When /^the client cd's to "(.*?)"$/ do |path|
+  capture_error do
+    step %Q(the client successfully cd's to "#{path}")
+  end
+end
+
+# As of Ruby 1.9.3-p125, Net::FTP#chdir('..') will send a CDUP.
+# However, that could conceivably change: The use of CDUP not
+# required by the FTP protocol.  Therefore we use this step to
+# ensure that CDUP is sent and therefore tested.
+
+When /^the client successfully cd's up$/ do
+  @client.raw 'CDUP'
+end
+
+When /^the client successfully cd's to "(.*?)"$/ do |path|
+  @client.chdir path
+end
+
+Then /^the current directory should be "(.*?)"$/ do |path|
+  @client.pwd.should == path
+end

data/features/step_definitions/error.rb

@@ -0,0 +1,87 @@
+def capture_error
+  yield
+  @error = nil
+rescue Net::FTPError => e
+  @error = e.message
+end
+
+Then /^the server returns no error$/ do
+  @error.should be_nil
+end
+
+Then /^the server returns a "(.*?)" error$/ do |error_message|
+  @error.should include error_message
+end
+
+Then /^the server returns a no such file error$/ do
+  step 'the server returns a "550 No such file or directory" error'
+end
+
+Then /^the server returns a login incorrect error$/ do
+  step 'the server returns a "530 Login incorrect" error'
+
+end
+
+Then /^the server returns a not logged in error$/ do
+  step 'the server returns a "530 Not logged in" error'
+end
+
+Then /^the server returns an access denied error$/ do
+  step 'the server returns a "550 Access denied" error'
+end
+
+Then /^the server returns a path required error$/ do
+  step 'the server returns a "501 Path required" error'
+end
+
+Then /^the server returns a not found error$/ do
+  step 'the server returns a "450 No such file or directory" error'
+end
+
+Then /^the server returns a syntax error$/ do
+  step 'the server returns a "501 Syntax error" error'
+end
+
+Then /^the server returns a mode not implemented error$/ do
+  step 'the server returns a "504 Mode not implemented" error'
+end
+
+Then /^the server returns an invalid mode error$/ do
+  step 'the server returns a "504 Invalid mode code" error'
+end
+
+Then /^the server returns a file structure not implemented error$/ do
+  step 'the server returns a "504 Structure not implemented" error'
+end
+
+Then /^the server returns an invalid file structure error$/ do
+  step 'the server returns a "504 Invalid structure code" error'
+end
+
+Then /^the server returns a bad sequence error$/ do
+  step 'the server returns a "503 Bad sequence of commands" error'
+end
+
+Then /^the server returns a type not implemented error$/ do
+  step 'the server returns a "504 Type not implemented" error'
+end
+
+Then /^the server returns an invalid type error$/ do
+  step 'the server returns a "504 Invalid type code" error'
+end
+
+Then /^the server returns a format not implemented error$/ do
+  step 'the server returns a "504 Format not implemented" error'
+end
+
+Then /^the server returns an invalid format error$/ do
+  step 'the server returns a "504 Invalid format code" error'
+end
+
+Then /^the server returns a command unrecognized error$/ do
+  step 'the server returns a "500 Syntax error, command unrecognized" error'
+end
+
+Then /^the server returns an unimplemented command error$/ do
+  step 'the server returns a "502 Command not implemented" error'
+end

data/features/step_definitions/file_structure.rb

@@ -0,0 +1,16 @@
+When /^the client successfully sets file structure "(.*?)"$/ do
+|file_structure|
+  @client.raw 'STRU', file_structure
+end
+
+When /^the client sets file structure "(.*?)"$/ do |file_structure|
+  capture_error do
+    step %Q'the client successfully sets file structure "#{file_structure}"'
+  end
+end
+
+When /^the client sets file structure with no parameter$/ do
+  capture_error do
+    @client.raw 'STRU'
+  end
+end