Add unit test for GEDCOM export error handling #43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request adds a unit test to ensure that the GEDCOM exporter command handles file write errors gracefully.
Description
The changes in this pull request include:
GedcomExporterTest
that extends the baseTestCase
class.setUp()
method, the test case fakes the local storage usingStorage::fake('local')
.testHandlingOfFileWriteErrors()
that mocks theStorage::put()
method to throw an exception, and then asserts that the GEDCOM export command outputs the expected error message and exits with a non-zero status code.tearDown()
method to close the Mockery instance and call the parent'stearDown()
method.Summary
The changes in this pull request include:
GedcomExporterTest
unit test classStorage::put()
method to throw an exceptionSuggested changes from Sweep Chat by @curtisdelicata. Continue chatting at https://sweep-chat-demo.vercel.app/c/daa6c803-2d05-428b-be8d-8d7baa695217.