Usetrace's weekly reporting feature helps you stay informed about your tests performance through comprehensive, data-rich email reports. These reports provide a visual summary of test executions, success rates, and team activity, making it easy to track trends and identify areas for improvement.
How It Works
Every Sunday, our system automatically generates a report for active projects with periodic reporting enabled. The reports contain data from the previous week (Monday to Sunday) and display various metrics through attractive and comprehensive charts.
Reports are delivered via email to all configured recipients for each project. Each report includes:
Overall success rate summary
Daily activity patterns
Success/failure trends by day
Team activity statistics
Configuration Options
Reports can be configured at the project level by going to Preferences -> Scheduling & Reporting:
Under the Periodic Reports section, you have a check to enable/disable the weekly reports for this project. Projects with that check on will generate the weekly reports.
Recipients list: You can add multiple team members to receive the reports.
Timezone settings: The report will use the project's general timezone to show data adjusted to your project's timezone
Understanding the Charts
Overall Stats
This section provides a snapshot of your testing performance:
Pass Rate: The pie chart will help you understand the number of passed tests compared to total execution, showing your test health.
Traces Executed: Total number of tests run during the reporting period
Build Performance: Breakdown of success, fail, and timeout percentages
Average Trace Timing: Performance metrics showing average runtime for all traces, successful traces, and error traces
Tags Used: Count of different tags both native to Usetrace (Smoke, Bugs, Regression, Flaky) and the custom ones used in your test suite
Trace Activity
This section displays when your tests are being run and their success rates (converted to the current project's timezone):
Lists the active time periods for each day of the week
Shows the success rate percentage for each time period
Helps identify patterns like "tests run on Friday afternoons have lower success rates"
The data is grouped by time ranges to help you correlate test performance with your team's working hours.
Weekly Trace Activity Heatmap
The heatmap visualizes your testing patterns throughout the week:
The horizontal axis represents hours of the day (0-23)
The vertical axis represents days of the week (Monday-Sunday)
Color intensity indicates activity level (lighter for fewer tests, darker green for more tests)
This visualization makes it easy to spot when your team is most active and if there are periods with unusually high or low activity. The heatmap shows data for up to 6,000 test executions by performance reasons.
Successes vs Fails
This multi-part section compares success and failure metrics across different timeframes:
This Week: Show total tests run, success count, and fail count with a pie chart visualization
This Month: Displays the current month's testing totals with success/fail breakdown
Last Quarter: Provides long-term performance data with quarterly success/fail statistics
Line Chart: Shows day-by-day success and failure rates throughout the week
This lets you compare short-term performance against longer-term trends to quickly spot anomalies or gradual changes in test reliability.
User Activity
This section highlights your team's contributions:
Most Active Creator(s): Lists team members who created the most traces that week
Most Active Editor(s): Lists team members who edited the most traces that week
For each person, shows:
Number of traces created/edited
Percentage change from the previous week
Trend indicators (▲ for increase, ▼ for decrease)
Project Activity
This section summarizes the overall project activity:
Trace Creator of the Week: Highlights the user who created the most new traces
Most Active Editor: Highlights the user who edited the most traces
New Traces Created: Total count of new traces added during the week
Traces Edited: Total count of traces modified during the week
Run Counter: Compares trace execution volume to the previous week with percentage change
Failure Counter: Compares test failures to the previous week with percentage change
This section helps track both team contribution and overall project health trends.
By leveraging these weekly reports, your team can maintain visibility into test performance, identify trends, and make data-driven decisions to improve your automation effectiveness.