#5 Reporting


In this section, we hook Usetrace’s testing reports to a Flowdock chat. We also take a deeper look at the information details for a trace run. This feature can be used to debug issues on your site.

Section outline:

1. Go To Settings

Click “Settings”.

2. Add Reporting

(1) Open “Scheduling & Reporting”.

(2) Add report for Flowdock.

(3) Change Flowdock “Send reports:” to “Always” and set the API token for you Flowdock flow

(4) Reports for Slack, JIRA and HipChat can also be added and configured.

(5) Go to Dashboard.

3. Batch Run On Dashboard

(1) Click Run all Traces. To run multiple traces at once, to make a batch run, you can manually click the Run button on the Dashboard or integrate Usetrace to your continuous integration (CI) system (Settings -> Automation).

(2) Notice the run queue

4. Dashboard Notifications

After a trace is run in a batch, the results appear as notifications on the Dashboard.

5. Flowdock

(1) Click Usetrace feed in Inbox.

(2) Information for a failed login trace run. Click the link “Login” to open the full details inside usetrace.com.

6. Details

(1) Image of the failed step and the fail message.

(2) Screenshot of the full browser when the fail happened.

(3) Click “Webdriver commands”.

7. Webdriver

Here’s the log of webdriver commands and responses that Usetrace has sent and received during the trace execution.

Click “Network”.

8. Network

The display of the network activity for the browser’s session. Activity is separated by each step. You can order the loaded resources by clicking on the headers.

All failed loads are highlighted.

Click “Trend”.

9. Performance History Graph

Shows the history of run times for this trace. Daily average is counted for the successful runs. Click a run to open the Network tab for that current run.