[API tests] Re-enable APIV1 and APIV2 API tests

[Prangshuman Das (t-prda)]

Review focus: mostly mechanical. Initialize sets a license-safe work date in each API test, and the JSON deletions re-enable tests. A few files have small fixture or isolation tweaks.

Re-enables the APIV1, APIV2, IRS 1099 and E-Document API tests that pass without area-specific fixes. Aligned with NAV master: only tests that NAV master also runs are re-enabled.

• API test Initialize sets a license-safe work date. Adds minimal fixture and isolation adjustments.
• Removes the APIV1/APIV2 exclusions, keeping only the entries fixed in the following area PRs and the two 139806 methods NAV master disables. Removes E-Doc 135575.

Related: AB#646383, AB#653393

Stack (each PR shows only its own layer; merge bottom first)

1. [API tests] Default to web service key authentication #12674 A: web service key auth (base: main)
2. [Expense tests] Re-enable Expense Agent API tests #12675 B: Expense API tests + clean test codeunit execution
3. [API tests] Re-enable APIV1 and APIV2 API tests #12676 C: re-enable APIV1/APIV2 API tests
4. [API tests] Simplify API test web service key handling #12890 Review fixes for A: simplify web service key handling
5. Area fixes: [API tests] Ensure VAT posting setup in API document fixtures #12677 D1 VAT fixtures → [API tests] Ensure cancellation reason codes in API sales document tests #12678 D2 cancellation reasons → [API tests] Handle localized purchase invoice payment discounts in APIV1 tests #12679 D3 localized discounts → [API tests] Set sales quote document and posting dates in API tests #12680 D4 quote dates → [API tests] Assign a number series to API vendor payment journals #12681 D5 journal numbering → [API tests] Ignore localized fields in API document comparisons #12682 D6 field comparison → [API tests] Return shipment PDF selection and pdfDocument test isolation #12683 D7 PDF documents → [API tests] Improve APIV1 fixture and verification reliability #12684 D8 APIV1 reliability

Experiments (on D8, do not merge): #12685 E single tenant, #12686 F no clean execution. Combined validation (do not merge): #12687, same tree as D8.

Platform: main already pins BCPlatform 30.0.56112.0, which includes the SQL connection-pool fix (AB#653457).

Note for CI: AL-Go's new-warning check needs a CI/CD baseline from the base branch, and features/* bases have none, so a PR build there fails with a 404. The current CI runs were triggered while these PRs targeted main, so their results are valid for the cumulative change.

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Style}$

The AL source file name uses a lowercase object-name segment (APIV2itemLedgEntriesE2E), which breaks the PascalCase ..al convention. Rename it to APIV2ItemLedgEntriesE2E.Codeunit.al.

Knowledge:

• microsoft/knowledge/style/file-name-object-type-pattern.md

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.50.6}

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Style}$

The file name uses a lowercase object-name segment (APIV2itemLedgEntriesE2E) while the declared codeunit is APIV2 - Item Ledg. Entries E2E. Rename the file to use the PascalCase object-name form, APIV2ItemLedgEntriesE2E.Codeunit.al, so the file-to-object mapping remains discoverable.

Knowledge:

• microsoft/knowledge/style/file-name-object-type-pattern.md

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.50.6}

[alexei-dobriansky]

Good Sense Reviewer - Round 2

Recommendation: Accept

What this PR does

This revision re-enables the APIV1, APIV2, IRS 1099, and E-Document API tests that are ready to run. It sets a license-safe work date, prepares fixtures before API calls, and keeps the remaining known failures excluded.

The full current diff was reviewed because the previous head was replaced. The APIV1 and APIV2 counterparts use consistent setup and isolation patterns, the purchase-order dates now follow the configured work date, and the retained disabled-test entries still map to valid test methods.

Status of previous suggestions

None.

New observations (commits since round 1)

None.

Risk assessment and necessity

Risk: Re-enabling 1,150 test exclusions broadens the CI surface, and several API tests disable isolation so external sessions can see committed fixtures. The fixtures are initialized before API activity, the paired API versions follow the same pattern, the remaining exclusions are valid, and all completed checks are green.

Necessity: Restoring these tests is needed to recover broad API regression coverage after the shared authentication and runtime prerequisites became available. The scope is appropriate because it re-enables the passing set and retains the known unrelated failures.

---

[AI-PR-REVIEW] version=1 promptVersion=4 system=github pr=12676 round=2 by=alexei-dobriansky at=2026-10-14T22:56:04.5286717Z lastSha=b301b04f49c6a39f4c9c8b333c77c64f613879ba reviewKey=051bc163d0b60e6d0fc21b4636c2c48c01a164b617be533004d91f5ac6a01f74 suggestions=none parentRound=1