auto-test-after-write

To run BSL syntax checks automatically after writing a module, you need a workflow that triggers post-write validation. This Skill verifies newly written 1C BSL modules by immediately checking syntax and ensuring they parse correctly before you commit changes.

Automated test discovery for 1C BSL modules works by finding related unit or integration tests using module-specific naming patterns. It then executes these discovered tests with deterministic filters, controlled timeouts, and parallel workers for fast feedback.

The best way to validate BSL modules before committing in 1C is to trigger post-write validation that checks syntax and runs targeted tests. This ensures instant confirmation that your code parses and related tests still pass before integration.

Yes, you need YaXUnit to run automated BSL tests in this workflow. The Skill requires YaXUnit execution and METR designer configuration validation to perform deterministic test processing and regression checks on your newly written modules.

Yes, you can use parallel test processing for BSL module validation. The Skill runs discovered tests with deterministic filtering, controlled timeouts, and parallel workers to provide fast feedback on your newly written 1C modules.

BSL regression testing may fail after a module write if the new code contains syntax errors or breaks existing tests. Running post-write validation with deterministic filters helps immediately catch these parsing issues and test failures before committing.