How do I correlate telemetry events with specific tests?

The skill mandates a 'DEBUG-TEST-START' marker at the beginning of every test procedure. This allows you to grep the telemetry.jsonl file and isolate all events triggered by a specific test.

What is the 'False Positive Problem' in AL testing?

It occurs when a test assertion passes (e.g., verifying a value) even though the code executed a different logic branch than intended. This skill uses telemetry to prove the correct path was actually taken.

What is the mandatory first line for every test procedure?

Every test must begin with FeatureTelemetry.LogUsage('DEBUG-TEST-START', 'Testing', ' ') to ensure all subsequent logs can be attributed to that specific test.

Can this skill help debug standard Business Central code I can't modify?

Yes. It includes a specific pattern for creating temporary event subscribers that emit telemetry from standard BC subsystems, providing visibility into internal execution paths.

Why must I remove the DEBUG-* telemetry logs after testing?

DEBUG telemetry is intended as temporary scaffolding to verify code paths during development. Leaving it in production code pollutes logs and indicates incomplete refactoring.

AL Test-Driven Development (TDD)

Name: AL Test-Driven Development (TDD)
Author: FBakkensen

byFBakkensen

セキュリティとテスト

Implements rigorous Red-Green-Refactor patterns for AL development using telemetry-based verification to ensure correct code path execution.

概要

The TDD skill optimizes Microsoft Dynamics 365 Business Central development by enforcing a strict Red-Green-Refactor cycle enhanced with temporary telemetry checkpoints. It solves the common 'False Positive' problem in AL testing—where assertions pass despite code taking an unintended logic path—by requiring developers to log and verify specific execution branches. The skill provides a comprehensive workflow for creating, verifying, and cleaning up debug instrumentation, and includes advanced patterns for debugging standard BC subsystems through temporary event subscribers.

主な機能

Prevents false positive test results through mandatory path verification
Enforces a structured Red-Green-Refactor workflow with automated Todo tracking
Uses temporary DEBUG-* telemetry to prove specific code path execution
Automates the cleanup process to ensure zero debug instrumentation enters production
Provides patterns for debugging standard BC subsystems via event subscribers
0 GitHub stars

ユースケース

Debugging opaque standard Business Central processes like pricing or posting engines
Developing complex AL business logic where specific branch execution must be verified
Building high-reliability test suites that guarantee both output correctness and path coverage

概要

主な機能

Prevents false positive test results through mandatory path verification
Enforces a structured Red-Green-Refactor workflow with automated Todo tracking
Uses temporary DEBUG-* telemetry to prove specific code path execution
Automates the cleanup process to ensure zero debug instrumentation enters production
Provides patterns for debugging standard BC subsystems via event subscribers
0 GitHub stars

ユースケース

Debugging opaque standard Business Central processes like pricing or posting engines
Developing complex AL business logic where specific branch execution must be verified
Building high-reliability test suites that guarantee both output correctness and path coverage