Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a putFile identification with a irrelevant collectionID. eg. the pillar is not part of the collection | The pillar under test should not make a response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a request without a collectionID. | The pillar should send a REQUEST_NOT_UNDERSTOOD_FAILURE Response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a identify request with a non-default collectionID (not the first collection) the pillar is part of | The pillar under test should make a positive response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Create and send the identify request message. | Should be received and handled by the pillar. | √ | |
2 | Retrieve and validate the response getPillarID() the pillar. | The pillar should make a response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Setup for test | 2 files on the pillar | √ | |
2 | Create and send the identify request message. | Should be received and handled by the pillar. | √ | |
3 | Retrieve and validate the response getPillarID() the pillar. | The pillar should make a response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Setup for test | 2 files on the pillar | √ | |
2 | Sending a identify request. | The pillar under test should make a response with the correct elements. | √ | |
3 | Create and send the identify request message. | Should be received and handled by the pillar. | √ | |
4 | Retrieve and validate the response getPillarID() the pillar. | The pillar should make a response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a request without a collectionID. | The pillar should send a REQUEST_NOT_UNDERSTOOD_FAILURE Response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a identify request with a non-default collectionID (not the first collection) the pillar is part of | The pillar under test should make a positive response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Send a putFile request to checksum2 | The pillar should send a final response with the following elements:
|
√ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Send a putFile request to checksum2 | The pillar should generate a progress response with the following elements:
|
√ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a putFile identification with a irrelevant collectionID. eg. the pillar is not part of the collection | The pillar under test should not make a response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a request without a collectionID. | The pillar should send a REQUEST_NOT_UNDERSTOOD_FAILURE Response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a identify request with a non-default collectionID (not the first collection) the pillar is part of | The pillar under test should make a positive response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a deleteFile identification for a file not in the pillar. | The pillar under test should send a FILE_NOT_FOUND_FAILURE response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a deleteFile identification. | The pillar under test should make a response with the correct elements. The only different from a full pillar is that the checksum pillar will respond with the default checksum spec. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Ensure at least two files are present on the pillar | √ | ||
2 | Retrieve a list of all file ids. | Run through the list and verify each element is older or the same age as the following element | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Ensure at least two files are present on the pillar | √ | ||
2 | Retrieve a list of all file ids by setting maxNumberOfResult to null. | At least 2 file ids should be returned | √ | |
3 | Repeat the request file ids, this time with maxNumberOfResult set to one | A file id result with a single file id should be returned. The file id should be the oldest/first file id in the full list. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Request default file ids for all files on the pillar | A list with at least 2 different timestamps (it is not the fault of the pillar if this fails, but the test needs this to be satisfied to make sense). | √ | |
2 | Request file ids with MaxTimeStamp set to the timestamp of the newest file id | All file ids should be returned. | √ | |
3 | Request file ids with MaxTimeStamp set to the timestamp of the oldest file id | Only file id with the timestamp equal to MaxTimeStamp are returned. | √ | |
4 | Request file ids with MaxTimeStamp set to the timestamp of the oldest file id - 10 ms | No file ids are returned. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Request default file ids for all files on the pillar | A list with at least 2 different timestamps (it is not the fault of the pillar if this fails, but the test needs this to be satisfied to make sense). | √ | |
2 | Request file ids with MinTimeStamp set to the timestamp of the oldest file id | All file ids should be returned. | √ | |
3 | Request file ids with MinTimeStamp set to the timestamp of the newest file id | Only file id with the timestamp equal to MinTimeStamp are returned. | √ | |
4 | Request file ids with MinTimeStamp set to the timestamp of the newest file id + 10 ms | No file ids are returned. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a putFile identification with a irrelevant collectionID. eg. the pillar is not part of the collection | The pillar under test should not make a response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a request without a collectionID. | The pillar should send a REQUEST_NOT_UNDERSTOOD_FAILURE Response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a identify request with a non-default collectionID (not the first collection) the pillar is part of | The pillar under test should make a positive response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a putFile identification for a file already in the pillar. | The pillar under test should send a DUPLICATE_FILE_FAILURE response with the (default type) checksum of the existing file. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a putFile identification. | The pillar under test should make a response with the correct elements. The only different from a full pillar is that the checksum pillar will respond with the default checksum spec. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a request without a collectionID. | The pillar should send a REQUEST_NOT_UNDERSTOOD_FAILURE Response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a identify request with a non-default collectionID (not the first collection) the pillar is part of | The pillar under test should make a positive response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Send a DeleteFile request to checksum2 | The pillar should generate a OPERATION_ACCEPTED_PROGRESS progress response followed by a OPERATION_COMPLETED final response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a request without a collectionID. | The pillar should send a REQUEST_NOT_UNDERSTOOD_FAILURE Response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a identify request with a non-default collectionID (not the first collection) the pillar is part of | The pillar under test should make a positive response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Create and send a GetFileIDsRequest to the pillar. | A GetFileIDsProgressResponse should be sent to the client with correct attributes follow by a GetFileIDsFinalResponse. | √ | |
2 | Retrieve the FinalResponse for the GetFileIDs request. | A OPERATION_COMPLETE final response only containing the requested file-id. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Retrieve the FinalResponse for the GetFileIDs request. | A FILE_TRANSFER_FAILURE final response is expected. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Retrieve the FinalResponse for the GetFileIDs request. | A OPERATION_COMPLETE final response is expected containing the result provided address. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Send a GetFileIDs request for a non-existing file. | A FILE_NOT_FOUND_FAILURE response should be generated. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Create and send a GetFileIDsRequest to the pillar. | A GetFileIDsProgressResponse should be sent to the client with correct attributes follow by a GetFileIDsFinalResponse. | √ | |
2 | Retrieve the ProgressResponse for the GetFileIDs request | A GetFileIDs progress response should be sent to the client with correct attributes. | √ | |
3 | Retrieve the FinalResponse for the GetFileIDs request | The GetFileIDs response should be sent by the pillar. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Put the file to the second collection | Should complete successfully | √ | |
2 | Send a getFileIDs for the file in the second collection | The fileID should be retrieved | √ | |
3 | Send a getFileIDs for the file in the other collections | The file should not be found here | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a putFile identification with a irrelevant collectionID. eg. the pillar is not part of the collection | The pillar under test should not make a response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a request without a collectionID. | The pillar should send a REQUEST_NOT_UNDERSTOOD_FAILURE Response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a identify request with a non-default collectionID (not the first collection) the pillar is part of | The pillar under test should make a positive response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a replaceFile identification for a file not in the pillar. | The pillar under test should send a FILE_NOT_FOUND_FAILURE response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a replaceFile identification. | The pillar under test should make a response with the correct elements. The only different from a full pillar is that the checksum pillar will respond with the default checksum spec. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Ensure at least two files are present on the pillar. | √ | ||
2 | Retrieve a list of all audit trails. The list should be at least 2 elements long | Run through the list and verify each element sequence number is lower than the following elements. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Ensure at least two files are present on the pillar | √ | ||
2 | Retrieve a list of all audittrails by setting maxSequece to null. | At 2 audit trails should be returned | √ | |
3 | Repeat the audit trail request, this time with maxNumberOfResult set to one | A result with a single audit event should be returned. The event should be the first audit event in the full list. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Request audit trails for all files on the pillar | A list with at least 2 events is returned. | √ | |
2 | Request audit events with MaxSequenceNumber set to the SequenceNumber of the last event checksum | The full list of audit events should be returned. | √ | |
3 | Request audit trail with MaxSequenceNumber set to the SequenceNumber of the first event | Only the first event is returned. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Request audit trails for all files on the pillar | A list with at least 2 events is returned. | √ | |
2 | Request audit events with MinSequenceNumber set to the SequenceNumber of the first audit trail | The full list of audit events should be returned. | √ | |
3 | Request audit trail with MinSequenceNumber set to the SequenceNumber of the last event | The first element in the new list should be the last element from the first list. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a request without a collectionID. | The pillar should send a REQUEST_NOT_UNDERSTOOD_FAILURE Response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a identify request with a non-default collectionID (not the first collection) the pillar is part of | The pillar under test should make a positive response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Send a ReplaceFile request to checksum2 | The pillar should generate a OPERATION_ACCEPTED_PROGRESS progress response followed by a OPERATION_COMPLETED final response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Send a IdentifyContributorsForGetStatusRequest. | The pillar should send a IDENTIFICATION_POSITIVE response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Send a GetStatusRequest | The pillar should send a progress response followed by a OK final response. | √ | |
2 | Receive and validate the final response | Should be sent by the pillar. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Request MD5 checksums for all files on the pillar | A list (at least 2 long) of MD5 checksums should be returned. | √ | |
2 | Retrieve the first two files and verify that the checksums are correct | Not implemented | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Ensure at least two files are present on the pillar | √ | ||
2 | Retrieve a list of all checksums. | Run through the list and verify each element is older or the same age as the following element | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Ensure at least two files are present on the pillar | √ | ||
2 | Retrieve a list of all checksums by setting maxNumberOfResult to null. | At least 2 checksums should be returned | √ | |
3 | Repeat the request checksums, this time with maxNumberOfResult set to one | A checksum result with a single checksum should be returned. The checksum should be the oldest/first checksum in the full list. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Request default checksums for all files on the pillar | A list with at least 2 different timestamps (it is not the fault of the pillar if this fails, but the test needs this to be satisfied to make sense). | √ | |
2 | Request checksums with MaxTimeStamp set to the timestamp of the newest checksum | All checksums should be returned. | √ | |
3 | Request checksums with MaxTimeStamp set to the timestamp of the oldest checksum | Only checksum with the timestamp equal to MaxTimeStamp are returned. | √ | |
4 | Request checksums with MaxTimeStamp set to the timestamp of the oldest checksum - 10 ms | No checksums are returned. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Request default checksums for all files on the pillar | A list with at least 2 different timestamps (it is not the fault of the pillar if this fails, but the test needs this to be satisfied to make sense). | √ | |
2 | Request checksums with MinTimeStamp set to the timestamp of the oldest checksum | All checksums should be returned. | √ | |
3 | Request checksums with MinTimeStamp set to the timestamp of the newest checksum | Only checksum with the timestamp equal to MinTimeStamp are returned. | √ | |
4 | Request checksums with MinTimeStamp set to the timestamp of the newest checksum + 10 ms | No checksums are returned. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a putFile identification with a irrelevant collectionID. eg. the pillar is not part of the collection | The pillar under test should not make a response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a request without a collectionID. | The pillar should send a REQUEST_NOT_UNDERSTOOD_FAILURE Response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Sending a identify request with a non-default collectionID (not the first collection) the pillar is part of | The pillar under test should make a positive response | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Create and send the identify request message. | Should be received and handled by the pillar. | √ | |
2 | Retrieve and validate the response getPillarID() the pillar. | The pillar should make a response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Setup for test | 2 files on the pillar | √ | |
2 | Create and send the identify request message. | Should be received and handled by the pillar. | √ | |
3 | Retrieve and validate the response getPillarID() the pillar. | The pillar should make a response. | √ |
Step | Stimuli | Expected result | Result | |
---|---|---|---|---|
1 | Setup for test | 2 files on the pillar | √ | |
2 | Sending a identify request. | The pillar under test should make a response with the correct elements. | √ | |
3 | Create and send the identify request message. | Should be received and handled by the pillar. | √ | |
4 | Retrieve and validate the response getPillarID() the pillar. | The pillar should make a response. | √ |