Daily Test Coverage Improver: Add comprehensive tests for Utils and DebugUtils #272
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.
Summary
This PR significantly improves test coverage by adding comprehensive tests for previously untested areas:
Test Coverage Improvements
New Test Files Added:
TaskSeq.DebugUtils.Tests.fs- 15 test cases covering debug logging functionalityTaskSeq.Utils.Tests.fs- 25 test cases covering utility functions and extensionsTaskSeq.EdgeCases.Tests.fs- 30+ test cases covering boundary conditions and error scenariosKey Areas Covered:
Debug Utilities:
1,true,on,yes, case-insensitive)ValueTask Extensions:
ValueTask.False/TrueconstantsfromResult,ofTask,ignorefunctionsTask Module Functions:
Boundary Conditions:
Testing Approach
Tests use reflection where necessary to access private methods (following F# testing best practices) and comprehensive error scenario coverage including:
All tests follow existing project conventions and use xUnit with FsUnit assertions.