{"query":"Refresh coverage after product change","corpusVersion":"local","generatedAt":"2026-09-13T04:41:25.494Z","results":[{"blockId":"coverage.refresh#refresh-coverage-after-product-change","pageId":"coverage.refresh","title":"Refresh coverage after product change","pageTitle":"Refresh coverage after product change","url":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh#refresh-coverage-after-product-change","markdownUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","sectionId":"refresh-coverage-after-product-change","kind":"task","productArea":"coverage_engineering","score":4668.9986722736785,"reasons":["search_match","title_match","display_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"# Refresh coverage after product change"},{"blockId":"coverage.refresh#task-steps-refresh-benchmark-coverage","pageId":"coverage.refresh","title":"Task steps: Refresh benchmark coverage","pageTitle":"Refresh coverage after product change","url":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh#task-steps-refresh-benchmark-coverage","markdownUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","sectionId":"task-steps-refresh-benchmark-coverage","kind":"task","productArea":"coverage_engineering","score":2690.742616688523,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"### Task steps: Refresh benchmark coverage\n\n1. Open the Benchmark's **Coverage Management** overview and identify which coverage claim is no longer supported.\n2. Review **Coverage Facets**. Update Dimensions, ontology values, Project Topics, or Case Construction Patterns only when the behavior model itself changed.\n3. Return to the **Case Pool**. Source, upload, draft, or synthesize candidate Cases for the missing or changed region.\n4. Inspect the candidates for source context, realistic inputs, duplication, and the intended coverage labels. Keep uncertain Cases out of benchmark use.\n5. Use **Coverage Management → Get Started** and the overview to update coverage guidance. Use **Case Review** and **Benchmark Datasets** to change selected Cases deliberately.\n6. Create a new Dataset Snapshot and Benchmark Version for the revised evidence boundary.\n7. Run a new evaluation when current candidate evidence is required. Compare it with older Runs using the named Benchmark Versions."},{"blockId":"coverage.refresh#object-and-state-changes","pageId":"coverage.refresh","title":"Object and state changes","pageTitle":"Refresh coverage after product change","url":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh#object-and-state-changes","markdownUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","sectionId":"object-and-state-changes","kind":"task","productArea":"coverage_engineering","score":1915.938588204048,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Object and state changes\n\nA refresh may change coverage-facet definitions, Case classifications, candidate Cases, selected benchmark Cases, and the next Snapshot. It does not rewrite an earlier Snapshot or make its Runs invalid. Older results remain evidence for their original version; the new version answers the current coverage question.\n\nIf only candidate behavior changed, keep the Benchmark Version fixed and run the new candidate against it. If the Case set, applicable standards, or coverage boundary changed, create a new Benchmark Version before interpreting a new Run as comparable."},{"blockId":"coverage.refresh#source-confidence","pageId":"coverage.refresh","title":"Source confidence","pageTitle":"Refresh coverage after product change","url":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh#source-confidence","markdownUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","sectionId":"source-confidence","kind":"task","productArea":"coverage_engineering","score":1606.978694949017,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Source confidence\n\nCode-backed: Coverage Management, Coverage Facets, the Case Pool, Case Review, Benchmark Datasets, and Dataset Snapshots establish the current sequence and the objects that can change. The decision that a product change requires a refresh remains a team-owned interpretation of evidence."},{"blockId":"coverage.refresh#when-to-use-it","pageId":"coverage.refresh","title":"When to use it","pageTitle":"Refresh coverage after product change","url":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh#when-to-use-it","markdownUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","sectionId":"when-to-use-it","kind":"task","productArea":"coverage_engineering","score":1602.9628821768206,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## When to use it\n\nRefresh coverage when new Cases reveal an unrepresented behavior, source material or product behavior changes, experts qualify an earlier assumption, or a governed Policy changes which situations matter. This is a coordinated workflow across Coverage Engineering—not a single refresh action."},{"blockId":"coverage.refresh#common-failure-modes","pageId":"coverage.refresh","title":"Common failure modes","pageTitle":"Refresh coverage after product change","url":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh#common-failure-modes","markdownUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","sectionId":"common-failure-modes","kind":"task","productArea":"coverage_engineering","score":1573.8209023306943,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Common failure modes\n\n- Treating refresh as a single button and missing a changed facet, Case set, or Snapshot boundary.\n- Rewriting a historical Snapshot instead of creating a new one.\n- Adding generated or newly sourced Cases to a Benchmark before review.\n- Comparing Runs without naming whether the candidate, Benchmark Version, or both changed.\n\n{% example-demo title=\"A newly supported exception\" %}\nA support assistant gains an approved exception path for one account tier. The team adds or revises the account-tier ontology, sources Cases for eligible and ineligible requests, reviews them in Case Review, updates the coverage guidance, and changes the selected Benchmark Dataset. A new Snapshot freezes the revised membership. Previous Runs still describe the old rule; new Runs evaluate the approved exception boundary.\n{% /example-demo %}"},{"blockId":"coverage.refresh#success-criteria","pageId":"coverage.refresh","title":"Success criteria","pageTitle":"Refresh coverage after product change","url":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh#success-criteria","markdownUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","sectionId":"success-criteria","kind":"task","productArea":"coverage_engineering","score":1561.2112437698513,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Success criteria\n\n- The changed product reality maps to an explicit coverage facet or documented boundary.\n- Candidate Cases have enough source context to be reviewed and are not mistaken for in-use benchmark evidence.\n- The new selected set addresses the gap without silently removing still-important behavior.\n- The new Snapshot names a reproducible evidence boundary.\n- Comparisons distinguish candidate changes from Benchmark Version changes."},{"blockId":"coverage.refresh#related-troubleshooting-pages","pageId":"coverage.refresh","title":"Related troubleshooting pages","pageTitle":"Refresh coverage after product change","url":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh#related-troubleshooting-pages","markdownUrl":"https://teammately.ai/docs/coverage-engineering/coverage-refresh.md","sectionId":"related-troubleshooting-pages","kind":"task","productArea":"coverage_engineering","score":1560.3206609363776,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Related troubleshooting pages\n\n{% related-card-grid title=\"Diagnose refresh problems\" %}\n- [Stale Dimensions](/docs/troubleshooting/stale-dimensions)\n- [Unbalanced coverage](/docs/troubleshooting/unbalanced-coverage)\n- [Synthetic Cases That Feel Unrealistic](/docs/troubleshooting/unrealistic-synthetic-cases)\n{% /related-card-grid %}"}]}