XAT: making concurrent test results trustworthy
Follow worker crashes and missing results through discovery, process scheduling, fixtures, method deadlines, and report validation.
XAT · Python API testing
Follow discovery and report validation through concurrent failures, deadlines, and missing results.
Implemented unittest-based discovery, process concurrency, per-method deadlines, logs, and JSON reports; the toolkit remains in active development.
Problem
Follow discovery and report validation through concurrent failures, deadlines, and missing results.
My work
Defined scope and execution behavior; collaborated with AI on implementation and code review.
Engineering choice
Separate method outcomes from batch completeness. The parent reconciles planned work, worker messages, and process exits so a missing result cannot silently become a success.
Project articles
All articles →START HERE
Who cleans up after test preparation fails? unittest and XAT
Follow partial setup, cleanup exceptions, and worker termination to understand cleanup registration, retained errors, and resource lifetime.
XAT concurrency: method isolation, fixture scope, and deadline boundaries
Compare method and file subprocesses through shared fixtures, then follow discovery isolation, checkpoints, and parent-driven termination.
XAT reports: separating failure, missing results, and exit codes
Follow assertion failure, cleanup errors, and a worker crash through multiple issues, completeness, task identity checks, and command exit codes.