fix: Implement tap.todo(), fix tap.skip.test() to create test objects, and ensure tap.only.test() works correctly

- tap.todo.test() now creates proper test objects marked as todo
- tap.skip.test() creates test objects instead of just logging
- tap.only.test() properly filters to run only marked tests
- Added markAsSkipped() method for pre-test skip marking
- All test types now contribute to accurate test counts
- Updated documentation to reflect these fixes

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
2025-05-26 04:07:05 +00:00
parent c98bd85829
commit 7aaeed0dc6
4 changed files with 34 additions and 88 deletions

View File

@@ -304,14 +304,16 @@ tstest --changed
- Trend analysis
- Flaky test detection
### Known Issues to Fix
- **tap.todo()**: Method exists but has no implementation
- **tap.skip.test()**: Doesn't create test objects, just logs (breaks test count)
### Recently Fixed Issues
- **tap.todo()**: Now fully implemented with test object creation
- **tap.skip.test()**: Now creates test objects and maintains accurate test count
- **tap.only.test()**: Works correctly - when .only tests exist, only those run
### Remaining Minor Issues
- **Protocol Output**: Some protocol messages still appear in console output
- **Only Tests**: `tap.only.test()` exists but `--only` mode not fully implemented
### Next Recommended Steps
1. Add Watch Mode - high developer value
2. Implement Custom Reporters - important for CI/CD integration
3. Fix known issues: tap.todo() and tap.skip.test() implementations
4. Implement performance benchmarking API
1. Add Watch Mode (Phase 4) - high developer value for fast feedback
2. Implement Custom Reporters - important for CI/CD integration
3. Implement performance benchmarking API
4. Add better error messages with suggestions