Read the activity report

See how much testing and bug work was done on a project, and by whom.

In short

The activity report answers how much testing and bug work was done on a project, and by whom - not how healthy it is. API Tester's testing and Boards' bugs and stories show side by side for the same project and period.

Before you start

Steps

  1. Open Analytics, open the dashboard switcher in the title and choose "Activity".
  2. Choose the Project - one, or All projects (summed) for every project you can see.
  3. In an organization, optionally choose a Team to narrow the projects to those shared with it and its sub-teams.
  4. Set the Period (30 days by default) and the Person: Everyone, Only me or a name.
  5. Press "Open as report" to keep, download or schedule the same numbers.

Testing

Unique APIs tested, Tests created, Test executions, Requests created, Regressions detected (runs that turned a passing request into a failing one), Security checks and Performance checks. These are counts of activity, not verdicts. For what is failing now, run API project health.

Bugs and stories

Stories created, Bugs reported, Bugs accepted, Bugs rejected, Duplicate bugs and Fixes verified (bugs whose fix was confirmed). A Severity distribution counts the accepted bugs. Many high-severity reports with few accepted usually means triage is behind, not that the reports were wrong.

Good to know

If something goes wrong

Related