Add unit tests for handling invalid LiteDB files #2507
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.
Description
This PR adds four unit tests to handle scenarios where LiteDB attempts to open invalid database files and streams:
Issues
These tests are intended to address issue #2501.
Bugs Discovered
Test_AddDatabase_InvalidDatabase:
LiteDB.LiteException
to be thrown.Test_AddDatabase_InvalidDatabase_LargeFile:
LiteDB.LiteException
to be thrown.System.ArgumentOutOfRangeException
was thrown.Test_AddDatabase_InvalidDatabase_MemoryStream:
LiteDB.LiteException
to be thrown.System.NotSupportedException
was thrown.Test_AddDatabase_InvalidDatabase_LargeFile_MemoryStream:
LiteDB.LiteException
to be thrown.System.ArgumentOutOfRangeException
was thrown.These findings indicate that LiteDB is not handling invalid files and streams as expected, leading to different types of exceptions or no exceptions at all.