test: add comprehensive unit tests for Template::Context#446
Draft
toddr-bot wants to merge 1 commit into
Draft
Conversation
79 subtests covering the full public API: constructor configuration, template() resolution (blocks, blkstack, providers, prefixes), process()/include()/insert(), throw()/catch() argument forms, localise/delocalise, visit/leave, reset, define_block/filter/vmethod/view, filter caching, plugin loading, debugging, AUTOLOAD, and DESTROY. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
79 unit tests for
Template::Context, the runtime engine that ties all TT components together.Why
Context is the central module handling template resolution, processing, plugin/filter loading, exception handling, and variable scoping — yet it only had integration-style tests via template processing. Direct unit tests catch edge cases and serve as executable documentation.
How
Tests exercise every public method directly:
Testing
🤖 Generated with Claude Code
Quality Report
Changes: 1 file changed, 950 insertions(+)
Code scan: 1 issue(s) found
t/unit-context.t:0— 950 lines addedTests: passed (OK)
Branch hygiene: clean
Generated by Kōan post-mission quality pipeline