Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problem: Create a Fail Transfer Compliance Test Set #28

Open
ross-spencer opened this issue Mar 14, 2018 · 2 comments
Open

Problem: Create a Fail Transfer Compliance Test Set #28

ross-spencer opened this issue Mar 14, 2018 · 2 comments

Comments

@ross-spencer
Copy link
Contributor

To fail verify transfer compliance (at present) all you need is a single empty folder. We can create a structure like this so that folks can observe that behaviour:

FailTransferCompliance/
├── README.md
└── TransferThisFolder

1 directory, 1 file
qubot pushed a commit that referenced this issue Mar 14, 2018
@ross-spencer
Adds a test case to Fail Transfer Compliance
daa0508 
* Resolves #28
@sallain sallain mentioned this issue May 9, 2018
Closed
@ross-spencer
Copy link
Contributor Author

NB. this would be a good one to create a AMAUAT test for.

@ross-spencer
Copy link
Contributor Author

There is an investigation of some of the more straightforward ways through which this microservice can fail here: archivematica/Issues#897 (comment) cc. @sarah-mason may be of interest around understanding different microservice failure conditions: ref: artefactual/archivematica-docs#316.

@ross-spencer ross-spencer mentioned this issue Jan 15, 2020
Closed
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ross-spencer