Excerpt |
---|
Describes the tests needed to validate the Replace functionality. |
Basic replace
- Attempt to replace a file. The file should exist in the collection, providing the correct checksum for the new file.
- The new file should now be the one in the collection. Use the getChecksum client to verify this.
...
- Attempt to replace a file in the collection, providing the correct checksums, but a wrong url (the url validates, but no file is found).
- The user should be informed that the pillars were unable to locate the file at the given url.
Replace with returned checksums
- Replace a file with including the a request of a salted checksum calculated on the pillars, which should be returned.
- Check that the file is replaced correctly, and that the returned checksums are correct and consistent across the responses returned by the pillars).
Child pages (Children Display) | ||
---|---|---|
|