Page Comparison

...

Test for the general getFile functionality.

1. Attempt to get a file present in the system. The file should be returned to the supplied urlan 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 for get the file delivered at a specific location (use -l argument):
   1. Should deliver the file at the given location.

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 from with an unknown fileID. 
   
   1. An error should be returned informing the user that no pillar is able to deliver the file could not be foundfile.
2. Attempt to get a file from an unexisting 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.

...