THE DEVELOPER WORKFLOW

From a failing response to a test Bob can use.

BugProof gives developers a concrete starting point for repair: the exact contract difference, an editable regression test, and a focused IBM Bob task.

Capture the request

Enter the endpoint, method, request body, and the observed response. Use a redacted example.

State the contract

Add the HTTP status and JSON your service should have returned. BugProof shows the mismatched values.

Create the regression

Copy a Vitest test that asserts the expected response. Run it in your project before changing the implementation.

Work with IBM Bob

Copy the task into Bob IDE in your authorized repository. Review the proposed change, rerun the test, and preserve the actual results.

Open the workbench

Does the workbench call my API?

No. You paste expected and observed responses, and the comparison runs in your browser. The generated test runs against your service when you add it to your repository. The built-in example button calls only BugProof’s inventory API.

Does the site run IBM Bob?

Bob runs in the IDE with your repository and review. BugProof prepares a focused task for Bob. Bob IDE investigated and repaired our inventory example and authored its replay logic; the evidence vault has genuine task summaries.

Where does my input go?

The workbench keeps your pasted case in the current browser tab and creates files locally for copying or download. The guided inventory example stores its report draft in browser storage and sends only the selected quantity to BugProof’s own API.

What does the guided lab demonstrate?

A complete repair on a sample inventory service: run the original behavior, inspect Bob’s completed repair, and verify it with actual API responses and tests.

Bring evidence into the IDE.

Run the generated test before and after a change. Keep private data out of the example and review generated code before use.

SEE THE COMPLETE EXAMPLE

The inventory repair, end to end.

Our working lab shows how a report becomes a reproduction, Bob-assisted repair, and evidence. The case starts with five items and resets after each request.

Open the guided example

TAKE THE WORKFLOW INTO IBM BOB

A focused task template.

The workbench produces a version filled with your case. This general template is available if you want to adapt it yourself.

Investigate this inventory defect with IBM Bob.

Report: [describe what happened]
Input: [quantity, including its actual JSON type]
Starting stock: 5
Expected: only positive safe integer quantities may be reserved; never exceed stock; errors preserve inventory.

1. Reproduce the original failure with an unchanged regression test.
2. Explain the root cause using the actual source.
3. Repair the implementation while preserving the original fixture.
4. Run the same regression plus boundary tests.
5. Save actual outputs, source revision, and Bob task-summary screenshots in bob_sessions/.

Use redacted data only. Do not claim results you did not run.