Systems | Development | Analytics | API | Testing

k6

Reliably Reliable

I Google’d the word “reliable” the other day. At the top of the results page was a definition from the Oxford Languages dictionary. I started thinking, what’s “reliable”? I glanced at my mobile phone. I felt it was pretty reliable. I can make and receive calls, I play games, battery life is pretty decent, photos are amazing… But it’s kind of new, so maybe that doesn’t count. It’s not really reliable, the jury’s still out.

Performance testing for beginners, with Matt Dodson (k6 Office Hours #65)

This week's show is about performance testing for beginners, where our technical writer, Matt Dodson, asks all the questions about load and performance testing that you were always afraid to ask. :) Matt joins Nicole van der Hoeven and Paul Balogh in discussing core principles of performance testing.

The future of k6, with the k6 CEO and CTO (k6 Office Hours #64)

We're talking about the future of k6 with CEO Robin Gustafsson and CTO Pawel Suwala. What's next for k6? What new features are we working on? What's the plan for further integrations with Grafana? What are the plans for the k6 team as we transition out of the honeymoon period after the Grafana acquisition?

Load testing Apache Kafka using k6, with Mostafa Moradian (k6 Office Hours #62)

Senior Software Engineer Mostafa Moradian joins us to talk about load testing Apache Kafka using k6 and the extension he created, called xk6-kafka. He describes what Kafka is, the basics of Kafka, and why he thinks load testing it is important. Mostafa works on the backend team at k6/Grafana Labs. // REFERENCES We used some video clips from these awesome people: And here are other resources we mentioned.

Resilience and chaos testing with SteadyBit and k6, with Benjamin Wilms (k6 Office Hours #61)

What is the difference between resilience testing and chaos testing? SteadyBit CEO and co-founder Benjamin Wilms talks about how to integrate SteadyBit with k6 for both resilience and chaos, and why he prefers "chaos testing" to "chaos engineering".