SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →Reference

ui5-fe-mockserver-tutorial

Ten exercises on @sap-ux/ui5-middleware-fe-mockserver, published for Devtoberfest 2025 as a repository to clone and a site to read, each exercise a Fiori elements app served from mock data instead of a backend.

Serving a Fiori elements app with no backend behind it means configuring the mockserver, and the ten exercises go through that one step at a time: data generated from the metadata, then custom JSON files, then JavaScript handlers that compute data and implement actions, then several services at once, then a write from one service's action handler into another's entity set, then per-tenant datasets and HTTP error responses. Exercise 8 drives the offline app end to end with wdi5, exercise 9 records live OData traffic with ui5-middleware-odata-recorder, and exercise 10 generates TypeScript types from the metadata with @sap-ux/fe-mockserver-admin. Each exercise is its own folder on its own port, and the first one makes a generated app offline by taking out the backend configuration the Fiori generator writes into ui5-mock.yaml, which otherwise routes requests past the mockserver. Setting the exercises up reads from a live service, so the CAP books service in ui5-call-action has to be running on http://localhost:4004, and the middleware being taught is SAP's, published from SAP/open-ux-odata.

Facts

Last push

Where it sits

Lives in
Demonstrates
UI5 testingUI5UI5 testingcapabilityProving 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.Build and dev-server toolingUI5Build and dev-server toolingcapabilityServing an app locally and building it for deployment — proxying a backend, transpiling, bundling, and shaping the result for whatever will host it.
Requires
ui5-call-actionui5-call-actionartifactThe CAP project whose BookshopService and ReviewsService the exercises read from: it supplies the metadata the apps are generated against, the data exercise 9 records, and the two service paths exercise 4 configures side by side.

Who is behind it

Marian ZeisMarian ZeisPersonMaintains this
In the atlas: maintains 35, contributes to 86, wrote 25
@marianfoo
maintainerNicolas LunetPersonContributes to this
In the atlas: contributes to 14
@nlunets
1 contributor

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

What it declares

Every artifact

Type
Sample
Origin
Independently maintained
Use as
A reference
Runtime
Node.js

As a sample

Form
A tutorial's companion code

Connections3

README

quoted from marianfoo/ui5-fe-mockserver-tutorial, read
marianfoo/ui5-fe-mockserver-tutorial/README.mdOn GitHub

Tutorial for using @sap-ux/ui5-middleware-fe-mockserver in SAP Fiori development.

SAP Community Blog Post: UI5 Middleware FE Mockserver in Practice — New Tutorial from Devtoberfest

Read this tutorial online (GitHub Pages): https://marianfoo.github.io/ui5-fe-mockserver-tutorial/

🚀 Two Ways to Use This Tutorial

excerpt, no licence read, read the rest, on GitHub

Details

Sources3
GitHub organisations and accountsdiscovered here, marianfoochecked
github.com/marianfoo/ui5-fe-mockserver-tutorialtree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
discovered viaGitHub organisations and accounts · marianfoo
first seen in the atlas
ecosystem and domainui5, developer-experience
Flavors1
Fiori elements
“This tutorial is based on **Fiori Elements List Report & Object Page** applications.” — marianfoo/ui5-fe-mockserver-tutorial — README, Fiori Application Prerequisiteschecked
Contributors1

From the repository’s contributor list, .

History in the atlas4
  1. form is tutorial, on the README's first line: "Tutorial for using `@sap-ux/ui5-middleware-fe-mockserver` in SAP Fiori development." The repository was published for Devtoberfest 2025 and the SAP Community post the README links calls it a tutorial from Devtoberfest, so workshop was considered and left out: form is one value, and what this presents itself as is a tutorial with exercise folders, not CodeJam material.
  2. The README's Prerequisites tell the reader to clone and run that CAP project before starting, and the fact was already in what_it_solves with no edge under it. artifact:marianfoo-ui5-call-action was a pending draft when this entry was written and is published now, so the plain link in the prose became a graph link in the same pass, as did ui5-middleware-odata-recorder.
  3. Sample with use_as reference, following artifact:sap-samples-manage-apis-codejam: a repository of exercises is evidence that something works and never an option to depend on. It demonstrates capability:ui5-testing because that capability's core coverage already names "an OData V2 mock server for a backend stand-in" as what SAP ships, and capability:ui5-build-tooling because the mockserver is registered as UI5 Tooling custom middleware in ui5-mock.yaml. compat.runtimes is the README's Required Tools, "**Node.js** (20 LTS or higher)". @sap-ux/ui5-middleware-fe-mockserver, the middleware being taught, has no entry of its own, so it stands in the prose as a code span and the README's own pointer to SAP/open-ux-odata is linked out. No licence is stated anywhere in the repository, so identity is absent.
  4. First seen.
For your agent
Ref
artifact:marianfoo-ui5-fe-mockserver-tutorial
JSON
/artifacts/marianfoo-ui5-fe-mockserver-tutorial.json
MCP
Connecting an agent