Please describe the problem you'd like to be solved.
Via @scollazo and discussions in Slack.
An important part of testing a new Archivematica release is taking a set of transfers known to work (or with known failure conditions) and making sure they pass or fail (x) or (y) mircroservices, and an AIP is created (or not) with certain properties. It would be good to automate this core part of testing so that testing can focus on outliers, new features, and testing new potential ways to make the software fall over.
Describe the solution you'd like to see implemented.
We want to explore the possibility of using the AMAUAT (acceptance-test) framework to create tests that will do this for arbitrary test-transfers and arbitrary test-transfer types.
Describe alternatives you've considered.
The AMAUAT framework is one possibility, but there might be others. A simple script using the API that monitors the logs, or reads from the UI and downloads and access an AIP may also do the trick. The idea would be to not get held up initially by the potential complexity of a solution, but find one that works and used in short-order and that can be built upon.
For Artefactual use:
Please make sure these steps are taken before moving this issue from Review to Verified in Waffle:
All PRs related to this issue are properly linked 👍
All PRs related to this issue have been merged 👍
Test plan for this issue has been implemented and passed 👍
Documentation regarding this issue has been written and it has been added to the release notes, if needed 👍
ross-spencer
commented
5 years ago
Please describe the problem you'd like to be solved.
Via @scollazo and discussions in Slack.
An important part of testing a new Archivematica release is taking a set of transfers known to work (or with known failure conditions) and making sure they pass or fail (x) or (y) mircroservices, and an AIP is created (or not) with certain properties. It would be good to automate this core part of testing so that testing can focus on outliers, new features, and testing new potential ways to make the software fall over.
Describe the solution you'd like to see implemented.
We want to explore the possibility of using the AMAUAT (acceptance-test) framework to create tests that will do this for arbitrary test-transfers and arbitrary test-transfer types.
Describe alternatives you've considered.
The AMAUAT framework is one possibility, but there might be others. A simple script using the API that monitors the logs, or reads from the UI and downloads and access an AIP may also do the trick. The idea would be to not get held up initially by the potential complexity of a solution, but find one that works and used in short-order and that can be built upon.
For Artefactual use: Please make sure these steps are taken before moving this issue from Review to Verified in Waffle: