You’ve built your report. It counts approved and resolved messages per topic in the reporting period, shows the messages behind each count, and lists the records that need review or were excluded. You also investigated and fixed an unexpected count yourself in Track Down a Surprising Count.
There’s one step left in the plan: hand the report over. Whoever uses it next should be able to run it, read it, and question a number without having to trust you or the code blindly.
In this short session, the mentor plays the support lead who asked for the report. You’ll walk them through it in seven steps:
- Explain how to use the report.
- Show an example input and its result.
- Trace one count back to its messages.
- Explain the fix you made in the last exercise.
- Name one concrete limitation of the report.
- Make a small change you haven’t seen before, and run it in the app.
- Put together a short hand-over note for the next reader.
It’s a conversation, not a test of every line, and it takes about fifteen minutes. Keep your report.js, the brief, and the report app open, because you’ll want to check things as you go:
