You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating extensions for k6 currently requires a deep understanding of how k6 works internally. The existing documentation doesn’t fully explain the process, and many developers have to dig through source code to figure things out. This is especially challenging for users who aren’t familiar with Go or who want to quickly build something custom.
Why this matters
Extensions are a powerful way to make k6 work with specific tools and systems—like proprietary databases or messaging platforms. But because the development process is unclear and complex, many users are discouraged from trying it. This limits what people can do with k6 and can push them toward other solutions. As we introduce features like Binary Provisioning and improve support in Grafana Cloud, making extension development easier becomes even more important.
What we want to build
We want to create clear, complete, and beginner-friendly documentation that walks users through building extensions in both Go and JavaScript. This will include explanations of the two approaches, guidance on when to use each, and step-by-step tutorials. Our goal is to make extension development something that anyone can do—even without a deep technical background.
What success looks like
More people should be able to build and share their own extensions without needing to reverse-engineer k6. Whether users are working with open source k6 or Grafana Cloud, they’ll have the resources they need to extend the platform confidently. This will help grow the community, unlock more use cases, and make k6 a more flexible performance testing tool overall.
The text was updated successfully, but these errors were encountered:
Creating extensions for k6 currently requires a deep understanding of how k6 works internally. The existing documentation doesn’t fully explain the process, and many developers have to dig through source code to figure things out. This is especially challenging for users who aren’t familiar with Go or who want to quickly build something custom.
Why this matters
Extensions are a powerful way to make k6 work with specific tools and systems—like proprietary databases or messaging platforms. But because the development process is unclear and complex, many users are discouraged from trying it. This limits what people can do with k6 and can push them toward other solutions. As we introduce features like Binary Provisioning and improve support in Grafana Cloud, making extension development easier becomes even more important.
What we want to build
We want to create clear, complete, and beginner-friendly documentation that walks users through building extensions in both Go and JavaScript. This will include explanations of the two approaches, guidance on when to use each, and step-by-step tutorials. Our goal is to make extension development something that anyone can do—even without a deep technical background.
What success looks like
More people should be able to build and share their own extensions without needing to reverse-engineer k6. Whether users are working with open source k6 or Grafana Cloud, they’ll have the resources they need to extend the platform confidently. This will help grow the community, unlock more use cases, and make k6 a more flexible performance testing tool overall.
The text was updated successfully, but these errors were encountered: