Seed data
In a UI5 app the service is often a mock server standing in for the OData backend, so the data here is what that mock server answers with: JSON files written by hand or generated from the metadata. Running the mock server itself is UI testingUI5 testingProving a UI still works — unit tests over controllers and formatters, integration tests that drive real controls, and end-to-end runs against a served app.SAP and community, narrow by design.
Overview
The OData V2 mock server, sap/ui/core/util/MockServer, answers from JSON files or produces random data from the service metadata it simulates when the files are left out. Apart from the framework, SAP publishes ui5-middleware-fe-mockserver, a UI5 dev server middleware that answers OData V2 and V4 requests of the Fiori elements templates it supports, with a generateMockData option.
Not covered: At values that fit the types. The OpenUI5 documentation says the generated data does not match the business scenario, so believable names and addresses are files someone writes.
No community artifact is documented here.
Artifacts
Nothing is mapped here yet.
Details
Coverage
For your agent
- Ref
capability:seed-data- JSON
- /capabilities/seed-data.json
- MCP
- Connecting an agent