| loio |
|---|
| 69d3cbd4150c4ffb884e788f7f60fd93 |
view on: demo kit nightly build | demo kit latest release
A mock server mimics one or more back-end services. It is used to simplify integration testing and to decouple UI development from service development. By using a mock server you can develop and test the UI even if the service in the back end is incomplete or unstable.
The mock server included with OpenUI5 mimics OData V2 back-end calls. It simulates the OData provider and is completely client-based, meaning that no network connectivity to a remote host is required. It intercepts HTTP calls made to the server and provides a fake output to the client. All this is transparent to data binding and the use of an OData model and feels like a real server. No changes are required on the OData model.
The OData V2 mock server provides mock services and also mock data. It supports randomly generated data based on the service metadata as well as mock data provided in JSON files.
The mock server only supports the JSON format for representing the resources it exposes, such as collections, entries, links, and so on.
For more information on the OData V2 mock server, see the topics given below.
The mock server functionality for OData V4 is included with CAP Node.js. For more information, see https://cap.cloud.sap/docs/guides/using-services#local-mocking.
-
OData Features Supported by the OData V2 Mock Server
List of OData version 2.0 features supported or not supported by the mock server -
Using Mock Data with the OData V2 Mock Server
Mock Data can be used when you start the development of an app as well as for testing and problem solving when the data service is not available or it requires effort to set up data services.
Related Information