Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Describes the tests needed to validate the Replace functionality.

Basic replace

  1.  Attempt to replace a file. The file should exist in the collection, providing the correct checksum for the existing file.
    1. The new file should now be the one in the collection. Use the getChecksum client to verify this.

Bad old file checksum

  1. Attempt to replace a file, providing the wrong checksum for the old file.
    1. The file shouldn't be replaced, and the user should be informed that the operation failed due to the invalid checksum for the old file.

Missing file replace

  1. Attempt to replace a file that does not exist in the collection.
    1. The user should be informed that the operation failed because the file did't exist.

Replace with returned checksums

  1. Replace a file with including the a request of a salted checksum calculated on the pillars, which should be returned.
    1. Check that the file is replaced correctly, and that the returned checksums are correct and consistent across the responses returned by the pillars).

Open issues

key priority summary type created

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels