Christina, I'm unaware of any way to implement plugin tests into ASpace's existing test infrastructure. What we did was write RSpec tests outside of the ASpace release, which start the application (with our plugins), populate it with data via the API, and check the outputs of common tasks against fixtures. There's probably a better way of doing this (e.g. packaging the tests in the plugin directory, and having RSpec pull them out, instead of having them all in a big spec directory), but so far this has worked for us.
Thanks, --Alex On Tue, Feb 25, 2020 at 1:56 PM Cortland, Christina Rosalie < [email protected]> wrote: > Hi all, > > We wanted to explore adding automated tests for our locally developed > plugins and were curious how other institutions approached this. I know > ArchivesSpace has its own test suite that folks who develop on > ArchivesSpace can use, but how do institutions who develop their own > plugins test their custom functionality, especially when upgrading to a new > ASpace release? > > Thanks, > > Christina Cortland > Software Development > > UNC-Chapel Hill Libraries > > Pronouns: she/her > > _______________________________________________ > Archivesspace_Users_Group mailing list > [email protected] > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 [email protected]
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
