Slide 3 of 4

Where to go next

After baseline: stress, spike, soak

Diagram: baseline test supports stress, spike, and soak testing, then automation in pipelines

LevelTest typeQuestionWhere you are
FoundationBaseline“What does normal look like?”You are here
NextStress“Where does performance degrade?”After baseline
NextSpike“Can we survive a traffic burst?”After baseline
NextSoak“Does anything break over hours?”After baseline

Refer to the k6 test types guide for stress, spike, and soak patterns once your baseline is stable.

Extensions

Extend k6 with official and community add-ons when you need extra protocols, outputs, or integrations.

Further reading

Documentation

Community

Script

You have a solid foundation. Here’s where to go from here.

When you want to move past baselines, the k6 documentation on test types walks through stress, spike, soak, and related patterns. Read that after your baseline is stable, because those scenarios still compare against what normal looks like.

The k6 documentation is the definitive reference for everything from executors to custom metrics. The community forums are a great place to ask questions and see how other teams approach performance testing.

To connect k6 results with metrics, logs, or traces in your observability stack, start with the k6 guides on results and outputs, then follow the integrations that match your Grafana Cloud or self-managed setup.