![](/assets/png/tour/getting-started/wizard-1.png)
Getting started
![](/assets/png/pages/dashboards-latest.png)
Building dashboards
![](/assets/png/pages/results-bar.png)
Request and test results
![](/assets/png/tour/suites/suites.png)
Suites and configuration
![](/assets/png/pages/organisation.png)
Organisations and users
![](/assets/png/pages/account-billing.png)
Account management
Requests and test results
Each test logs information about the request, response, and assertions.
This page can be found by clicking any individual result in the console
This page can be found by clicking any individual result in the console
![Each test logs information about the request, response, and assertions. <br/>This page can be found by clicking any individual result in the console](/assets/png/pages/result.png)
Keeping data safe
By default the "Authorization" header and response payloads are not stored
Retention policy
All accounts have retention limits, in which case some information may eventually expire
Full screen
Most sections can be full-screened for closer inspection
Test result disputes
If you disagree with a result, please get in touch so we can fix the test suite (You can skip the test in the mean time)
Writing queries for test results
Use the results tab to query requests and test results without committing to a dashboard
Click rule on the left of the suite page to reach this page
Click rule on the left of the suite page to reach this page
What are queries?
Queries are written in a proprietary DSL inspired by SQL
Is there a learning curve?
If you read the query guide or are already familiar with SQL, the auto-completion should carry you the rest of the way