How do I know a project made of test coverage is finished?

Tares marks a project finished when you say it is: after the last milestone the orchestrator asks whether the project is finished, and your answer that it is done closes it. Tares marks the project Done with your own words and moves it to the finished list on the Crew page. Stopping the crew is a separate step, tares factory crew down.

How it works

The finish is a question to you, backed by a record you can read at any time.

• Milestones carry acceptance checks. The spec session turns your goal into a spec, a plan and milestones, and each milestone has acceptance checks. In the worked example, the first milestone was tests and CI on the branch: Vitest, unit tests for the babysitting logic, and a CI check on every pull request.
• Each ticket is reviewed and merged. In that example, a builder worked through the tickets one at a time. It made a branch, did the work and opened a pull request. The reviewer posted a verdict on every pull request, and once the verdict passed and CI was green, the builder merged.
• Each milestone ends with a question. The orchestrator brings you the choices the crew made on its own during the milestone, called assumptions, in one question. You keep them or not.
• The last milestone ends with the finish question. The orchestrator asks whether the project is finished. You answer in the orchestrator’s session. In the example, the person deployed the project first and answered that it was fully deployed, working, and done.
• Tares records the outcome. It marks the project Done with those words, every ticket merged, and moves it to the finished list on the Crew page.

The answer is yours to give. You decide whether the project is done, and the project page shows what you decide it on. For a walk through one full project, see A project, end to end.

Set it up

1. Check the requirements from Get started, then bring up the crew and plan the project:

   tares factory crew up
   tares factory spec "what you want to build"

2. Write the acceptance checks into the milestones during the spec session, so each milestone says what finished looks like. For a project about test coverage, that is the place to state the tests and CI checks you expect.

3. Open the Crew page in the console, at http://127.0.0.1:8787/crew on a local Tares, to follow the crew and the projects it holds. Open the project page to see the steps Spec, Build, Review and Done, and a progress bar with one segment per ticket.

4. Check the folds on the project page before you answer. Tickets shows each ticket with its pull request and review rounds. Decisions shows every question the crew asked you and your answer. Assumptions shows every choice the crew made on its own and whether you kept it.

5. When the orchestrator asks whether the project is finished, answer in its session. Say it is done, and add anything you checked, such as a deploy. Tares stores your words, up to 4,000 characters, in the Decisions fold.

6. When no project is left, the orchestrator asks whether to stop the crew. Stopping is its own step:

   tares factory crew down

   This stops every station. Run tares factory crew up when you have the next project. Tares keeps the projects, tickets and answers.

What you get

• A project marked Done with your own words, and every ticket merged.
• The project in the finished list on the Crew page. Open projects stay listed with their builders, and finished ones fold below.
• A project page that stays as the record of the whole build: the spec, the plan, the milestones with their acceptance checks, each ticket with its pull request and review rounds, and your decisions.
• A crew that keeps running until you stop it. Marking a project Done does not stop any station, and tares factory crew down does not change the project’s state.
• The projects, tickets and answers kept after you stop the crew, so the crew carries on from them next time.

When something else fits

• To reopen a finished project, hand it to the crew again, for example with a follow-up spec.
• To change direction while a project is building, talk to the orchestrator. You do not need to wait for the finish question.
• If you are not sure the project is done, do not answer yet. The project stays open until you do, and the Tickets and Decisions folds show what is left.

Related