Run any Skill in Manus with one click

buoyient-mock-mode

Stars4

Forks0

UpdatedMarch 27, 2026 at 22:22

How to set up local mock mode for manual testing of apps that use buoyient, so the app runs against fake server responses without a real backend. Use this skill when the user wants to run their app with mock data, set up a developer toggle for fake/real server, create a local testing mode, build a demo mode, configure mock responses at runtime, or test the app manually without a backend. Also trigger when the user mentions mock mode, fake server, demo mode, local testing mode, or developer toggle in the context of buoyient or SyncableObjectService.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

lauren2020

lauren2020/buoyient

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name

buoyient-mock-mode

description

Read the guide at docs/mock-mode.md for the complete, up-to-date instructions on setting up local mock mode for manual testing. That file is the authoritative reference and is kept in sync with the actual codebase.

Key points to remember:

Mock mode works by setting Buoyient.httpClient (in com.elvdev.buoyient.globalconfigs) to a mock-backed HTTP client before creating any services — no changes to service classes needed.
Use MockEndpointRouter from the :testing module to register mock HTTP handlers.
Use MockServerStore for stateful mock mode with realistic CRUD behavior.
TestConnectivityChecker should be set to online = true in mock mode.
Conflict simulation uses SyncableObjectRebaseHandler (not SyncableObjectMergeHandler).
Include all fields that SyncUpConfig.fromResponseBody() expects in mock responses — missing fields will cause it to return SyncUpResult.Failed.RemovePendingRequest.
Scope the :testing dependency to debug builds with debugImplementation.

More from this repository

same repository

buoyient-integration-testing

lauren2020/buoyient

How to write automated integration tests for SyncableObjectService implementations using buoyient's testing module. Use this skill when the user wants to test a buoyient service, write unit or integration tests for sync behavior, test online/offline paths, verify mock server responses, assert on pending request queues, or test sync-up/sync-down flows. Also trigger when the user mentions TestServiceEnvironment, MockEndpointRouter, MockResponse, or asks about testing offline-first sync logic.

How to create and register new SyncableObjectService implementations using the buoyient offline-first sync library. Use this skill whenever the user wants to add a new data type or service to an app that uses buoyient, create a syncable model, build CRUD operations with offline support, set up background sync for a new entity, or integrate a new API endpoint with buoyient's sync engine. Also trigger when the user mentions SyncableObject, SyncableObjectService, ServerProcessingConfig, or asks about offline-first data patterns in a Kotlin/Android context.

2026-03-304

buoyient-setup

lauren2020/buoyient

How to set up and install the buoyient offline-first sync library in an Android app. Use this skill when the user wants to add buoyient to their project, configure dependencies, set up initialization, register services for background sync, or integrate buoyient into an existing Android app. Also trigger when the user mentions adding buoyient as a dependency, setting up offline sync, configuring WorkManager for sync, or asks about BuoyientInitializer, Buoyient.registerServices, or SyncWorker setup.

2026-03-304

buoyient-integration-testing

name

buoyient-mock-mode

description

Key points to remember:

Mock mode works by setting Buoyient.httpClient (in com.elvdev.buoyient.globalconfigs) to a mock-backed HTTP client before creating any services — no changes to service classes needed.
Use MockEndpointRouter from the :testing module to register mock HTTP handlers.
Use MockServerStore for stateful mock mode with realistic CRUD behavior.
TestConnectivityChecker should be set to online = true in mock mode.
Conflict simulation uses SyncableObjectRebaseHandler (not SyncableObjectMergeHandler).
Include all fields that SyncUpConfig.fromResponseBody() expects in mock responses — missing fields will cause it to return SyncUpResult.Failed.RemovePendingRequest.
Scope the :testing dependency to debug builds with debugImplementation.