Codeunit 130400 "CAL Test Runner"

Base Application · System.TestTools.TestRunner · BC23-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnBeforeRunTests(var CALTestLine: Record "CAL Test Line") (integration)

Procedures

• AddTestMethod(FunctionName: Text[128])
• InitCodeunitLine()
• UpdateCodeunitLine(IsSuccess: Boolean)
• InitTestFunctionLine()
• UpdateTestFunctionLine(IsSuccess: Boolean)
• TryFindTestFunctionInGroup(FunctionName: Text[128]): Boolean
• CountTestCodeunitsToRun(var CALTestLine: Record "CAL Test Line"): Integer
• UpdateTCM(): Boolean

Plus 5 local procedures.

Triggers

OnRun, OnBeforeTestRun, OnAfterTestRun

Relations

• runs on Table 130401 “CAL Test Line”

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

• Codeunit 130401 “CAL Test Management” (11 calls: CloseWindow → ISTESTMODE, CountTestCodeunitsToRun → ISTESTMODE, InitCodeunitLine → ISTESTMODE, …)
• Codeunit 9990 “Code Coverage Mgt.” (2 calls: RunTests → Start, RunTests → Stop)
• Codeunit 130403 “CAL Test Runner Publisher” (1 call: OnBeforeTestRun → SetSeed)

Called by

• Codeunit 130401 “CAL Test Management” (2 calls: AddTestLine → (object), RunSuite → (object))

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "CAL Test Runner"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.