pablochacin
pablochacin
Since https://github.com/grafana/xk6-exec/pull/30 the `Command` function returns a custom error that includes the `stderr` (which is the scope of the PR according to its description) but also the `ProcessState`. Exposing in...
When building an extension, the k6 version built is not the one specified in the extension's go.mod but the latest (or the one defined in the build command) Workarounds: 1....
## What? Creates a bridge between the internally used `afero.Fs` library and golang's standard `fs.FS` and use it in the `k6deps` library. ## Why? `afero.FS` will eventually be removed from...
## What? integrates the logic of binary provisioning into the k6 root command. ## Why? Presently, the logic of binary provisioning happens before the k6 root command is executed. This...
## What? Use the loadsource function for dependency analysis ## Why? Presently, binary provisioning uses its own logic for loading the input for dependency analysis. This logic has some shortcomings...
## What? Analyze if the built-in extensions satisfy the dependencies before provisioning a new custom binary ## Why? Binary provisioning is available in any k6 binary, including those with built-in...
Presently, the binary provisioning is integrated as an alternative execution path at the beginning of the main function, before the k6 root command is executed. This approach has the advantage...
The binary provisioning logic searches the arguments received by k6 for the input script if any. Currently this logic use the extension to identify this argument. However, k6 allows arbitrary...
The binary provisioning can use a dependencies manifest to define the default versions for the dependencies required to execute a test. This is useful when multiple tests require the same...
Currently the launcher receives a provision function as a parameter. This function returns a `commandExecutor` that satisfies the dependencies. Transform this function into an interface to ease of debugging and...