# `src snapshot test`


## Flags

| Name | Description | Default Value |
|------|-------------|---------------|
| `-dump-requests` | Log GraphQL requests and responses to stdout | `false` |
| `-get-curl` | Print the curl command for executing this query and exit (WARNING: includes printing your access token!) | `false` |
| `-insecure-skip-verify` | Skip validation of TLS certificates against trusted chains | `false` |
| `-since` | duration ago to look for healthcheck data | `1h0m0s` |
| `-summary-path` | path to read snapshot summary from | `src-snapshot/summary.json` |
| `-trace` | Log the trace ID for requests. See https://sourcegraph.com/docs/admin/observability/tracing | `false` |
| `-user-agent-telemetry` | Include the operating system and architecture in the User-Agent sent with requests to Sourcegraph | `true` |


## Usage

```
'src snapshot test' uses exported summary data to validate a restored and upgraded instance.

USAGE
	src login # site-admin authentication required
	src [-v] snapshot test [-summary-path="./src-snapshot-summary.json"]

ASSESSING RESULTS
	The outputs of the test is supposed to be used only as a reference indicator of whether or not the instance is in a healthy state.

	It generally does not give a definitive result, though if an issue is found that the test deems may be critical, the command will exit with status 1.

SNAPSHOT SUMMARY
	The snapshot summary to assert against ('-summary-path') should be generated by 'src snapshot summary'.

TEST DATA
	Use '-dump-requests' to see what data is requested to perform tests.

```