E8 - Developer/tester productivity (data setup, mocking, scope narrowing)

[jgebal]

Target release or timeframe

No response

Scope and goals

Problem

Setting up test data (row-level and bulk), mocking/stubbing existing data structures, and narrowing a test's scope to relevant data/code are all currently manual, repetitive work for test authors.

Proposed direction

• Helper add-ons for test data setup, both row-by-row and bulk scale.
• Design and implement mocking/stubbing of existing data structures.
• Document (and where possible, tool-support) strategies for narrowing test scope.

Depends on

Largely additive - doesn't require Phase 0 to land first, so contributions can start whenever bandwidth allows.

Tracking

• Test data setup for test suit utPLSQL#1334
• Mocking/stubbing of existing data structures utPLSQL#1377
• Document strategies for narrowing test scope utPLSQL#1378

Open questions for the community

No response