Skip to content

Rewrite 'Why llmock' to lead with the problem #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jpr5 merged 1 commit into from
Mar 5, 2026
Merged

Rewrite 'Why llmock' to lead with the problem #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -946,10 +946,11 @@ <h1>Deterministic <span class="highlight">mock LLM</span> server for testing</h1
<section id="features" class="reveal">
<div class="container">
<span class="section-label">Why llmock</span>
<h2 class="section-title">Everything you need to test AI integrations</h2>
<h2 class="section-title">Stop paying for flaky tests</h2>
<p class="section-desc">
Built for E2E test suites where multiple processes — your app, agent workers, framework
runtimes — all need to hit the same mock endpoint.
Tests that hit real LLM APIs — OpenAI, Gemini, Anthropic — cost money, time out, and
produce non-deterministic results. llmock replaces those calls with immediate,
deterministic responses from a real HTTP server any process on the machine can reach.
</p>

<div class="features-grid">
Expand Down
Loading