Describes the tests needed to validate the GetFile functionality.

Basic functionality

Test for the general getFile functionality (Upload a file to test on first)

  1. Attempt to get an existing file from any pillar:
    1. Should be delivered to the file in the directory, where the client is run.
  2. Attempt to get a file from a specific pillar (use -p argument):
    1. Should be delivered to the file in the directory, where the client is run.
  3. Attempt to get the file delivered to a specific directory or file (use -l argument):
    1. Should deliver the file at the given directory or file.

Badcase tests

The following bad case scenarios should be tested to validated that the system handles the requests grazefully, eg. doesn't crash components and sends a informative error message.

  1. Attempt to get a file with an unknown fileID. 
    1. An error should be returned informing the user that no contributors is able to deliver the file.
  2. Attempt to get a file from an unexisting/unknown collection.
    1. Should get an error immediately from the client.
  3. Attempt to get a file from a pillar, which does not exist.
    1. Should get an error immediately from the client.
  4. Attempt to get a file from a checksum-pillar.
    1. The pillar should deliver a negative response.

Open issues