docs: clarify relationship with TestableIO.System.IO.Abstractions #835
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.



Added a comprehensive section to the README explaining the relationship between Testably.Abstractions and TestableIO.System.IO.Abstractions to address user confusion about when to use each library.
What this PR addresses
Users were confused about:
Changes made
New section: "Relationship with TestableIO.System.IO.Abstractions" that includes:
Interface compatibility explanation: Both libraries use the same
IFileSysteminterfaces, so production code doesn't need changes when switching between themDecision criteria: Clear guidance on when to use each library:
Migration guide: Step-by-step instructions with code examples showing how to switch from TestableIO to Testably:
The documentation maintains a respectful tone toward both projects while clearly explaining their different capabilities and use cases.
Fixes #471.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.