The basic recipe for testing the import/export utility and import/export verification tool follows:

1. Start up an empty Fedora
2. Load or /fcr:restore a dataset
3. Export the all or some of the dataset with the import/export utility
4. Verify the export with the verification tool
5. Start up a new Fedora (same or different port and context)
6. Import the exported resources with the import/export utility
7. Verify the import with the verification tool

Variations

The above recipe can be varied in the following ways:

1. For #2: In addition to custom, scripted ingest datasets, the "additional_datasets" are available for /fcr:restore
2. For #3: All of the configuration options should be tested
   1. With and without binaries (-b)
   2. Using default and aptrust bagit profiles
   3. Using inbound references (-i)
   4. Using membership predicates (-p)
   5. Overwriting tombstones (-t)
   6. With authorization (-u)
   7. Exporting external content (-x)
3. For #5: Start up the destination Fedora on a different port and with a different context, example
4. For #6: Use both the command line options and the auto-generated config file

Tests

Tester	Fedora Version	Import/Export Version	Verify Version	Dataset (detail below if custom)	Export Options	Export Verify Options	Source Fedora port & context	Destination Fedora port & context	Import Options	Import Verify Options	Success?	Notes
Jim Coble	4.7.2	0.1.1-SNAPSHOT-d4780ca2	master branch at 839cb8b	Small portion of production-like data loaded locally via Hydra framework	-c (config file contains -m export, -b, -p ldp#contains, -r, -d, rdfLang text/turtle)	none except config file	8984/rest	8984/rest	-c (same config file as used for export except for -m import)	none except config file	mixed – no errors on export or import - export verify successful, import verify mismatches (expected due to server-managed triples)	Exported entire repo; wiped repo; imported entire repo
Longshou Situ	4.7.2	1.1-SNAPSHOT-d4780ca2	master branch at commit bfd6fa1	plant patent (/fcr:restored from plants.tar.gz)	Command-line: -b, -g[default|aptrust], -i, -p, -x	-l, -g, -v	8080/fcrepo/rest	8686/f4/rest	Command-line: -b, -g[default|aptrust], -i, -p, -t	-l, -g, -v	mixed – import/export works as expected except 403 status found with inbound reference import and limitation on import/export verify	The plant patent dataset restored from plants.tar.gz has resource reference (<http://localhost:8080/fcrepo/rest/initialize>) in three of the records under /audit (for example, http://localhost:8080/fcrepo/rest/audit/c0/c8/af/98/c0c8af98-72a3-4ce0-96f0-aaf9ac2aa161). When exporting with binary excluded, those three records with non-existing resource reference won't be exported.
Jim Coble	4.7.2	0.1.1-SNAPSHOT-d4780ca2	master branch at 839cb8b	Small portion of production-like data loaded locally via Hydra framework	-c (config file contains -m export, -b, -p ldp#contains,#isMemberOfCollection, -i -r, -d, rdfLang text/turtle)	none except config file	8984/rest	8984/rest	-c (same config file as used for export except for -m import)			Unable to locate Jira server for this macro. It may be due to Application Link configuration. Import fails with error reported in above issue