---
title: "First test complete | Grafana Labs"
description: "Debrief after completing the first k6 test learning path"
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

## First test complete!

**What you accomplished:**

- Installed k6 on your machine
- Wrote a test script with HTTP requests and checks
- Ran a test locally and read the terminal output
- Sent results to Grafana Cloud k6
- Analyzed response time, throughput, and error rate in dashboards

## Skills unlocked

| Skill           | You can now                                                |
|-----------------|------------------------------------------------------------|
| Script writing  | Write k6 test scripts in JavaScript                        |
| Local execution | Run tests from the terminal and read results               |
| Cloud reporting | Stream results to Grafana Cloud for dashboards and history |
| Metric reading  | Interpret http\_req\_duration, http\_reqs, and checks      |

## Examine your results

Before moving on, look at the test results you just produced and consider:

- **p95 latency.** Was it higher or lower than you expected? What in the system or test data could explain that value?
- **Ramp-up vs steady state.** Did response times change as VUs increased? If yes, what does that suggest about capacity or queueing?
- **Check pass rate.** Were all checks at 100%? If any failed, what response shape or timing would explain it?
- **Your own system.** If you tested your own endpoint instead of QuickPizza, what p95 would you call too slow for that route?

These notes feed the threshold choices you will make in the next module.

## What’s next

You have test results, but no way to know if they’re “good.” In the next module, you’ll define what good looks like by establishing a performance baseline with automated pass/fail thresholds.