Page Comparison

...

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

• Attempt to get an existing file from any pillar:
  • Should be delivered to the file in the directory, where the client is run.

bin/bitmag.sh get-file -c integrationtest1 -i DefaultFile

• Attempt to get a file from a specific pillar (use -p argument):
  • Should be delivered to the file in the directory, where the client is run.

bin/bitmag.sh get-file -c integrationtest1 -i DefaultFile -p sbtape2

• Attempt to get the file delivered to a specific directory or file (use -l argument):
  • Should deliver the file at the given directory

...

• • or file.

bin/bitmag.sh get-file -c integrationtest1 -i DefaultFile -l ../NewNameFile

Bad case tests

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

• Attempt to get a file with an unknown fileID. 
  
  • An error should be returned informing the user that no contributors

...

• • are able to deliver the file.

bin/bitmag.sh get-file -c integrationtest1 -i UnknownFileName

• Attempt to get a file from

...

• a non-existing/unknown collection.
  • Should get an error immediately from the client.

bin/bitmag.sh get-file -c yourcollectionhere -i DefaultFile

• Attempt to get a file from a pillar, which does not exist.
  • Should get an error immediately from the client.

bin/bitmag.sh get-file -c integrationtest1 -i DefaultFile -p pillar-of-eternity

• Attempt to get a file from a checksum-pillar.
  • The pillar should deliver a negative response.

bin/bitmag.sh get-file -c integrationtest1 -i DefaultFile -p checksum2

...