xk6-grpc

Warning

Starting k6 version v0.49 the code of the k6/x/grpc extension is part of the k6/net/grpc of the main k6 repository. Please contribute and open issues there. This repository is no longer maintained.

This extension is re-designing of the k6's GRPC module that also should bring new features like GRPC streaming (it's available in the k6 as k6/experimental/grpc).

The extension code copied from the original k6's GRPC module. The module documentation is available here.

The new stream's functionality (more examples you can find in the examples folder):

import { Stream } from 'k6/x/grpc'

// Stream(client, method)
// - client - already initialized and connected client with the loaded definitions
// - method - a gRPC method URL to invoke.
const stream = new Stream(
  client,
  'foo.BarService/sayHello'
)

// A `stream.on` method adds a new handler for different kind of the events.
// 
// Currently supported: 
// `data`  - triggered when the server send data to the stream
// `error` - an error occurs
// `end`   - triggered when the server has finished sending the data
// You could register multiple handlers for the same kind event.
stream.on('data', message => {
  // server send data, processing...
})

// Write data to the stream
stream.write({ message: 'foo' })

// Signals the server that the client has finished sending the data
stream.end()

Requirements

• Golang 1.19+g
• Git
• xk6 (go install go.k6.io/xk6/cmd/xk6@latest)
• curl (downloading the k6 core's linter rule-set)

Getting started

1. Build the k6's binary with the module:

$ make build

2. Run the GRPC demo server in a separated terminal:

$ make grpc-server-run

3. Run the example:

$ ./k6 run examples/grpc_client_streaming.js

Contributing

Contributing to this repository is following general k6's contribution guidelines since the long-term goal is to merge this extension into the main k6 repository.

However, since right now there are two modules, k6/net/grpc and k6/experimental/grpc, that have similar functionality (the experimental module started as a copy), and not sharing the code, there is a specialty exists that forces us to backport (or forward port) changes to shared functionality (e.g., bug fixes) between modules.

We don't expect every contributor to do that and are happy to do that for you, but if you want to do that by yourself, you can do that.

Testing

To run the test you can use the make test target.

Linting

To run the linter you can use the make lint target.

Important

By default there is golangci-lint config presented. Since the long-term goal is to merge the module back to the grafana/k6 we use the k6's linter rules. The rule set will be downloaded automatically while the first run of the make lint or you could do that manually by running make linter-config.