Navigate
Before you change a program, see what the change touches. The Code Map answers which tests run this pattern, which active procedures are implemented and what depends on what, from the program itself: VBA modules, IG-XL sheets and digital patterns, with C/C++ or Python alongside.
Re-cyclize a pattern and the map names the test code whose pattern-start calls load it, a link that lives inside the code where no import scanner looks.
Every procedure the TestInst sheet calls, reconciled against the procedures the program's modules define. Anything missing is listed by name.
Select a file and see what it depends on, what uses it and what it exports, with any quality findings on that file.
The map is built from the code, not from a text search. Dependencies are extracted per language, so every edge comes from a call, include or import, never from a name that happens to appear in the text. Same inputs, same answer.
| Artefact | Dependency signal | Why it matters |
|---|---|---|
| VBA modules (.bas / .cls / .frm) | Real calls and references between modules: qualified calls, unqualified calls and Call statements. | Which module breaks when you change this one. |
| Digital patterns (.atp) | Pattern-start calls in VBT source that name their pattern file, resolved to the .atp files in the repo. | Re-cyclize a pattern and the map names the modules whose pattern-start calls name it. |
| IG-XL sheets | Mapped alongside the code; the TestInst sheet drives active-function coverage. | The program's structure, not just its code. |
| C / C++, Python, TypeScript / JavaScript | Import and include statements per language. Go, Rust and C# files are listed, not linked. | Mixed-language test benches map in the same table. |
The TestInst sheet names the VBT procedure each test instance calls: the procedures that actually run on the tester. Coverage reconciles that list against the procedures the program implements and gives the number an IG-XL engineer thinks in: of the active procedures, how many have an implementation? Anything active but unimplemented is listed by name.
Measured on the demonstration project's generated program, where no dependency graph is drawn (see Boundaries).
The same dependencies render as a graph: files that import nothing local on the left, top-level consumers on the right, in a deterministic layout. Graph and table are two views of one map, and isolated files hide behind a toggle so the view shows dependency signal only.
Every repository sync rebuilds the map from what is actually in the repository. Quality findings overlay the same table, a truncated read is labelled truncated, and a map that is re-indexing, failed or stale says so instead of presenting itself as current.
The map feeds the IG-XL agent. A workbook the agent reads in Excel is stored in the project and appears here with its sheets, its VBA modules and active-function coverage. From any file, ask the agent about it: ATE·IQ assembles that file's context and opens the chat with a question ready to send: what the file does, what it depends on and what uses it. When the Context Curator picks a file for the agent, the local files it depends on come with it, from the same extracted dependencies the map draws.