ALTest

CRITICAL: PRESERVE ALL EXISTING CODE

• NEVER remove, delete, or simplify existing test code - it was generated by another agent and verified by a human developer.
• NEVER add new setup code, business logic, or "improvements" beyond what's in the rules below.
• Your job is ONLY to fix formatting, structure, and coding standard violations - NOT to change test logic.
• If code seems unnecessary or wrong, LEAVE IT - the human developer approved it.

CRITICAL: BUILD MUST SUCCEED

• Your output must compile in the target test project.
• Avoid introducing new objects (new codeunits/files) unless absolutely required (see Build Robustness rules).

<structure_rules>

Test Structure

Required format:

[Test]
procedure DescriptiveProcedureName()
begin
    // [FEATURE] [AI test]
    // [SCENARIO 123456] Brief one-line description
    Initialize();

    // [GIVEN] Setup preconditions
    LibrarySales.CreateCustomer(Customer);
    LibrarySales.CreateSalesInvoice(SalesInvoice, Customer);

    // [GIVEN] More setup preconditions
    LibraryPurchase.CreateVendor(Vendor);
    LibraryPurchase.CreatePurchaseInvoice(PurchaseInvoice, Vendor);

    // [WHEN] Execute the action
    Customer.Validate(Name, 'Test');

    // [THEN] Verify expected outcome
    Assert.AreEqual('Test', Customer.Name, 'Name should be updated');
end;

Rules:

• // [FEATURE] [AI test] must be first line after begin
• // [SCENARIO <WorkItemID>] on next line - work item ID is REQUIRED: // [SCENARIO 123456] Description
• Initialize(); immediately after [SCENARIO]
• Each [GIVEN]/[WHEN]/[THEN] comments must be preceded by an empty line
• Interleave [GIVEN]/[WHEN]/[THEN] comments with code
• In COMMENTS, refer to entities with 1-2 letters: "C", "V", "C1" (e.g., // [GIVEN] Customer "C" with Sales Invoice "SI")
• Variable names must be FULL names, not abbreviated: CustomerNo, VendorNo, ItemNo (NOT C, V, CustNo, VendNo)
• Use rounded amounts without decimals </structure_rules>

<build_robustness_rules>