# Example repository

> Inspect a public example pull request and Twice run to learn how Estelle presents code review findings and running-app test results.

Use the example repository when you want to see Estelle's output before connecting your own code. It contains a small bill-splitting app called Tabby, an intentionally flawed pull request, and a recorded browser-test run.

The repository is [uqeu/estelle-example](https://github.com/uqeu/estelle-example). The app is a static page with a JavaScript module and tests, so you can read the whole example without setting up services or secrets. Its published page is [uqeu.github.io/estelle-example](https://uqeu.github.io/estelle-example/).

Reading the example does not connect it to your account or start any work.

## Inspect a pull request review

Open [pull request #1](https://github.com/uqeu/estelle-example/pull/1). The change rounds each person's share of a bill to whole cents.

The intentional bug is that every share is rounded independently. Leftover cents are not distributed, so the displayed shares can add up to less than the original bill. The added test uses an amount that divides evenly, which means the test can pass while the rounding bug remains.

Use the pull request to see how **Prism** presents a review:

- Read the review summary for the overall verdict.
- Open inline findings to see the file and line behind each problem.
- Compare the finding with both the implementation and its test.
- Treat the review as input to your own decision. Prism does not approve, request changes, or merge the pull request.

The first review ran before the repository index was ready and included findings that a later review did not retain. Both passes are part of the pull request's history. A fresh repository connection can still be indexing; read an incomplete review as incomplete, not as a clean result or a confirmed defect.

To request another Prism review on your own pull request, comment `/estelle review`. See [Prism](https://docs.fatelabs.ca/prism) for review verdicts, settings, and incomplete-review states.

## Inspect a browser-test run

Open the recorded [Twice run](https://github.com/uqeu/estelle-example/blob/main/estelle/twice-run.md), then compare it with the [test plan](https://github.com/uqeu/estelle-example/blob/main/estelle/twice-contract.json).

The plan records the user journeys and their expectations. The run records what Twice did in the browser and which journeys passed, failed, or remained suspected. This distinction matters: a suspected problem needs investigation, while a journey that could not run is not a pass.

The recorded run tested the live page built from `main`, not the pull request branch. It therefore could not detect the pull request's rounding bug. When you evaluate a Twice result, check which URL and which version of the app it exercised.

## Use the right result for the question

| Question | Where to look | Limit to keep in mind |
|---|---|---|
| Does this code change contain a logic problem? | Prism's review and the pull request diff | An incomplete review is not a clean review. |
| Can a user complete a journey in the running app? | Twice's journeys, expectations, and outcomes | The result applies to the app version and environment Twice visited. |
| Did the repository's tests pass? | The pull request checks | A passing test can miss behavior it does not assert, as this example shows. |

## Try the same workflow on your code

### Connect and index a repository

Follow the [Quickstart](https://docs.fatelabs.ca/quickstart). Install the Estelle GitHub App when you want pull request reviews or builds that open pull requests.

### Review a real change

Open a pull request yourself, or complete [Your first task](https://docs.fatelabs.ca/first-task). Read the diff, checks, and Prism findings together rather than relying on any one result.

### Test a running app

Open **Twice** in the dashboard and enter a staging or preview URL. Review the proposed journeys before the run, then inspect the outcome for each journey. Use a test account, never a real customer or administrator login.

## Related

- [Prism](https://docs.fatelabs.ca/prism): Learn how to read and retry a pull request review.
- [Twice](https://docs.fatelabs.ca/twice): Plan and run browser tests against your own app.
- [Quickstart](https://docs.fatelabs.ca/quickstart): Index your first repository and ask a cited question.