Seed data
In ABAP development and test data lives in the system's own tables, so it is entered by hand, kept in eCATT test data containers, or generated by ABAP code that fills them, with localised providers for names and addresses.
Overview
eCATT keeps test data apart from test scripts in test data containers, whose parameters describe the data and whose variants hold the values.
Not covered: At values someone entered. A test data container holds what was typed into its variants; believable names and addresses, and the volume a stress test needs, are generated by code written on top.
The repository here is independent; how it relates to eCATT test data containers has not been assessed.
Artifacts
Details
Coverage
For your agent
- Ref
capability:seed-data- JSON
- /capabilities/seed-data.json
- MCP
- Connecting an agent