> For the complete documentation index, see [llms.txt](https://sealights-docs.tricentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sealights-docs.tricentis.com/user-story-coverage/use-cases-by-persona/developers/code-review-facilitator.md).

# Code Review Facilitator

Elevate your code reviews with the power of real-time coverage insights. Utilize the User Story Coverage Report to identify areas lacking sufficient testing, proactively guiding reviewers towards potential blind spots.

***

## Step-by-Step Tutorial

<details>

<summary><strong>1. Access the User Story's / Subtask's Coverage</strong></summary>

* The code reviewer should open the user story or subtask in Jira and navigate to the "Coverage" tab.\
  ![](/files/8SAjhgdk7zWspzYY6Qks)\
  \
  **Note:** If the tab is missing, the user story deployment isn't complete. Refer to the[Deployment Guide](/user-story-coverage/technical-overview/deployment-guide.md) for further details.

</details>

<details>

<summary><strong>2. Deep Dive into Method List</strong></summary>

* Open the detailed coverage report to scrutinize individual methods.\
  \
  ![](/files/e9xKse2RQHW9boRC6Rm2)
* The report is on the User Story level. Find the relevant subtask in the report and open the method list.\
  \
  ![](/files/sMgoNx3O6tUzNT34aaTi)

</details>

<details>

<summary>3. Scan the Method List</summary>

* Quickly identify coverage gaps by looking for methods marked red (no tests) or orange (only unit tests).\
  \ <img src="/files/RAd7KpKkdLHV0E0GFhNT" alt="" data-size="original">
* Prioritize methods currently under review.

</details>

<details>

<summary>4. <strong>Assess Coverage</strong></summary>

* Use your organization's standards and testing strategy to judge if coverage is sufficient.
* **Important:** Some organizations run additional tests after code review. Only assess coverage for test types already executed.

</details>

<details>

<summary>5. <strong>Address Critical Gaps</strong></summary>

* If critical methods lack coverage, leave comments on the pull request or discuss directly with the developer.

</details>