chore(test): bump libs (#910)

Signed-off-by: Yvonnick Esnault <yvonnick.esnault@ovhcloud.com>

Author: yesnault

README.md

@@ -8,10 +8,10 @@ Venom is a CLI (Command Line Interface) that aims to create, manage and run your
 [![Discussions](https://img.shields.io/badge/Discussions-OVHcloud-brightgreen)](https://github.com/ovh/venom/discussions)
 <a href="https://gitpod.io/#https://github.com/ovh/venom"><img src="https://img.shields.io/badge/Contribute%20with-Gitpod-908a85?logo=gitpod" alt="Contribute with Gitpod"/></a>
 
-# Table of content
+# Table of contents
 
 - [🐍 Venom](#-venom)
-- [Table of content](#table-of-content)
+- [Table of contents](#table-of-contents)
 - [Overview](#overview)
 - [Installing](#installing)
   - [Install from binaries](#install-from-binaries)
@@ -61,10 +61,10 @@ Venom is a CLI (Command Line Interface) that aims to create, manage and run your
 # Overview
 
 Venom allows you to handle integration tests the same way you code your application.
-With Venom, testcases will be managed as code: the readability of the tests means that the tests are part of the code reviews. Thanks to that, write and execute testsuites become easier for developers and teams.
+With Venom, testcases will be managed as code: the readability of the tests means that the tests are part of the code reviews. Thanks to that, writing and executing testsuites becomes easier for developers and teams.
 
-Concretely, you have to write testsuite in a YAML file.
-Venom run executors (scripts, HTTP Request, web, IMAP, etc.) and apply assertions. 
+Concretely, you have to write a testsuite in a YAML file.
+Venom runs executors (scripts, HTTP Request, web, IMAP, etc.) and applies assertions. 
 It can also generate xUnit result files.
 
 <img src="./venom.gif" alt="Venom Demonstration">
@@ -73,7 +73,7 @@ It can also generate xUnit result files.
 
 ## Install from binaries
 
-You can find latest binary release from: https://github.com/ovh/venom/releases/latest/.
+You can find the latest binary release at: https://github.com/ovh/venom/releases/latest/.
 
 Example for Linux:
 
@@ -107,7 +107,7 @@ Version venom: v1.2.0
 
 # Docker image
 
-Instead of installing (and updating) Venom locally, Venom can be started as a Docker image with following commands. 
+Instead of installing (and updating) Venom locally, Venom can be started as a Docker image with the following commands. 
 
 Considering your testsuites are in `./tests` directory in your current directory and your test library is under `./tests/lib`, the results will be available under the `results` directory.
 
@@ -292,7 +292,7 @@ lib_dir: lib
 verbosity: 3
 ```
 
-Please note that the command line flags overrides the configuration file. The configuration file overrides the environment variables.
+Please note that the command line flags override the configuration file. The configuration file overrides the environment variables.
 
 
 # Concepts
@@ -302,7 +302,7 @@ Please note that the command line flags overrides the configuration file. The co
 A test suite is a collection of test cases that are intended to be used to test a software program to show that it has a specified set of behaviors.
 A test case is a specification of the inputs, execution conditions, testing procedure, and expected results that define a single test to be executed to achieve a particular software testing objective, such as to exercise a particular program path or to verify compliance with a specific requirement.
 
-In `venom` the testcases are executed sequentially within a testsuite. Each testcase is an ordered set of steps. Each step is based on an `executor` that enable some specific kind of behavior.
+In `venom` the testcases are executed sequentially within a testsuite. Each testcase is an ordered set of steps. Each step is based on an `executor` that enables some specific kind of behavior.
 
 In `venom` a testsuite is written in one `YAML` file respecting the following structure:
 
@@ -414,12 +414,12 @@ testcases:
     - result.alljson.hello ShouldContainSubstring World
 ```
 
-Notice the variable `alljson`. All variables declared in output are automatically converted in a json format with the suffix `json`. In the example above, two implicit variables are available: `displayjson.hello` and `alljson`.
+Notice the variable `alljson`. All variables declared in output are automatically converted into JSON format with the suffix `json`. In the example above, two implicit variables are available: `displayjson.hello` and `alljson`.
 
-Venom will load user's executors from the directory `lib/` relative to the testsuite path. You add executors source path using the flag `--lib-dir`. 
+Venom will load user-defined executors from the directory `lib/` relative to the testsuite path. You can add executor source paths using the flag `--lib-dir`. 
 Note that all folders listed with `--lib-dir` will be scanned recursively to find `.yml` files as user executors.
 
-The user defined executors work with templating, you can check the templating result in `venom.log`. In this file, if you see an error as `error converting YAML to JSON: yaml: line 14: found unexpected end of stream`, you probably need to adjust indentation with the templating function `indent`. 
+The user defined executors work with templating, you can check the templating result in `venom.log`. In this file, if you see an error such as `error converting YAML to JSON: yaml: line 14: found unexpected end of stream`, you probably need to adjust indentation with the templating function `indent`. 
 
 Example:
 
@@ -552,7 +552,7 @@ More examples are available [here](https://github.com/ovh/venom/tree/master/vari
 To be able to reuse a property from a teststep in a following testcase or step, you have to extract the variable, as the following example. 
 
 After the first step execution, `venom` extracts a value using a regular expression `foo with a ([a-z]+) here` from the content of the `result.systemout` property returned by the `executor`.
-Then this variable can be reused in another test, with the name `testA.myvariable` with `testA` corresponding to the name of the testcase. A default value could also be supplied if the variable can't be extracted from the output, which can commonly happen when parsing json output.
+Then this variable can be reused in another test, with the name `testA.myvariable` with `testA` corresponding to the name of the testcase. A default value could also be supplied if the variable can't be extracted from the output, which can commonly happen when parsing JSON output.
 
 ```yaml
 name: MyTestSuite
@@ -715,7 +715,7 @@ You may also include additional steps like a regular user defined executor.
 User assertions are executed in an entirely clean context, containing only the following variables:
 - `a`: the left operand
 - `b`: the (first) right operand
-- `argv`: the rights operands
+- `argv`: the right operands
 
 If you need to be compatible with the `input` syntax of user defined executors, you could use the `argv` as the default value and access these through the regular `input.*` syntax. 
 ```yaml
@@ -816,7 +816,7 @@ $ venom run --format=xml --output-dir="."
 $ venom run --output-dir="." --html-report
 ```
 
-Reports exported in XML can be visualized with a xUnit/jUnit Viewer, directly in your favorite CI/CD stack for example in order to see results run after run.
+Reports exported in XML can be visualized with an xUnit/jUnit Viewer, directly in your favorite CI/CD stack for example in order to see results run after run.
 
 # Advanced usage
 
@@ -846,7 +846,7 @@ testcases:
   - script: cat exec/testa.json
     info: "the value of result.systemoutjson is {{.result.systemoutjson}}"
     assertions:
-    - result.systemoutjson.foo ShouldContainSubstrin bar
+    - result.systemoutjson.foo ShouldContainSubstring bar
 ```
 
 ```bash
@@ -933,7 +933,7 @@ testcases:
 
 It is possible to iterate over data using `range` attribute.
 
-The following data types are supported, each exposing contexted variables `.index`, `.key` and `.value`:
+The following data types are supported, each exposing contextual variables `.index`, `.key` and `.value`:
 
 - An array where each value will be iterated over (`[]interface{}`)
   - `.index`/`.key`: current iteration index
@@ -1074,7 +1074,7 @@ Our awesome contributors:
 
 # License
 
-Copyright 2022 OVH SAS
+Copyright 2026 OVH SAS
 
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.

executors/amqp/README.md

@@ -1,6 +1,6 @@
 # Venom - Executor AMQP
 
-Step to publish / subscribe to AMQP 1.0 compatible broker (currently implemented by QPID and ActiveMQ, among others)
+Step to publish / subscribe to an AMQP 1.0 compatible broker (currently implemented by QPID and ActiveMQ, among others)
 
 ## Input
 

executors/couchbase/README.md

@@ -2,11 +2,11 @@
 
 Step to execute actions on a couchbase database using [github.com/couchbase/gocb/v2](https://pkg.go.dev/github.com/couchbase/gocb/v2) sdk.
 
-More information you can find [here](https://docs.couchbase.com/go-sdk/current/hello-world/start-using-sdk.html)
+You can find more information [here](https://docs.couchbase.com/go-sdk/current/hello-world/start-using-sdk.html)
 
 ## Connection
 
-To be possible use couchbase executor you need to specify at least the couchbase bucket (in case of no auth and running local).
+To use the couchbase executor you need to specify at least the couchbase bucket (in case of no auth and running local).
 
 A minimal couchbase configuration can be the following one:
 
@@ -48,7 +48,7 @@ For transcoder, you have the following options:
 
 See also [tests/couchbase.yml](../../tests/couchbase.yml) for executable examples.
 
-Couchbase can be used to store json structured data, but can store also binary and string types.
+Couchbase can be used to store JSON structured data, but can also store binary and string types.
 
 Example:
 
@@ -70,7 +70,7 @@ Get will retrieve documents by id. If the id can't be found the flag `found` wil
 
 By using flag `with_expiry` the expiration of the given entry will be returned (or will be zero if no expiration).
 
-by using flag `expiry` the get operation became `get and touch` and the option `with_expiry` will be ignored.
+By using flag `expiry` the get operation becomes `get and touch` and the option `with_expiry` will be ignored.
 
 ```yaml
 - type: couchbase
@@ -140,7 +140,7 @@ An expiration, in seconds, can be defined via field `expiry` to override the _de
 
 ### Upsert documents
 
-Upsert will insert or documents by id. It will set the flag `upserted` to true
+Upsert will insert or update documents by id. It will set the flag `upserted` to true.
 
 It is possible to preserve the original expiration (if any) via boolean field `preserve_expiry`.
 
@@ -183,7 +183,7 @@ Delete will remove by id. It will set the flag `deleted` to true in case the id
 
 Touch will update the object expiration for a given id. It will set the flag `touch` to true in case the id has been found.
 
-An `expiry` in seconds can be specified to be used. Unless it will use the global `expiry`.
+An `expiry` in seconds can be specified to be used. Otherwise it will use the global `expiry`.
 
 ```yaml
 - type: couchbase
@@ -201,7 +201,7 @@ An `expiry` in seconds can be specified to be used. Unless it will use the globa
 
 ### Check if document exists
 
-The command `exists` check if the document id exists or not. It will set a boolean flag `found` with the status.
+The command `exists` checks if the document id exists or not. It will set a boolean flag `found` with the status.
 
 ```yaml
 - type: couchbase

executors/dbfixtures/README.md

@@ -20,11 +20,11 @@ In your yaml file, you declare your step like this
   - folder optional
  ```
 
-- `schemas` is a list of paths to several `.sql` file that contains the schemas of the tables in your database. If specified, the content of every file will be executed before loading the fixtures.
+- `schemas` is a list of paths to several `.sql` files that contain the schemas of the tables in your database. If specified, the content of every file will be executed before loading the fixtures.
 - `files` parameter is only used as a fallback if `folder` is not used.
-- `migrations` is a folder path that contains SQL migrations files that can be used to initialize the database, instead of a list of schemas. **Note that if `schemas` is not empty, it will have precedence and migrations files will be ignored.**
+- `migrations` is a folder path that contains SQL migration files that can be used to initialize the database, instead of a list of schemas. **Note that if `schemas` is not empty, it will have precedence and migration files will be ignored.**
 - `migrationsTable` is the table used to store the migration version.
-- `skipResetSequences` is only used for PostgreSQL database, it control whether index should be reset (default) or not
+- `skipResetSequences` is only used for PostgreSQL databases, it controls whether the index should be reset (default) or not
 
 Example usage (_mysql_):
 ```yaml

executors/grpc/README.md

@@ -1,6 +1,6 @@
 # Venom - Executor Grpc
 
-Step for execute GRPC Request
+Step to execute a gRPC request
 
 Based on `grpcurl`, see [grpcurl](https://github.com/fullstorydev/grpcurl) for more information.
 This executor relies on the gRPC server reflection, which should be enabled on the server as described 
@@ -11,7 +11,7 @@ gRPC server reflection also does not properly work with `gogo/protobuf`: grpc/gr
 
 ## Tests
 
-Results of test are parsed as json and saved in `systemoutjson`. Status codes correspond 
+Results of tests are parsed as JSON and saved in `systemoutjson`. Status codes correspond 
 to the official status codes of gRPC.
 You can find what individual return codes mean [here](https://github.com/grpc/grpc/blob/master/doc/statuscodes.md).
 
@@ -23,14 +23,14 @@ In your yaml file, you can use:
   - url mandatory
   - service mandatory: service to call
   - method mandatory: list, describe, or method of the endpoint
-  - data optional: data to marshal to json and send as a request
+  - data optional: data to marshal to JSON and send as a request
   - headers optional: data to send as additional headers
   - connect_timeout optional: The maximum time, in seconds, to wait for connection to be established. Defaults to 10 seconds
   - default_fields optional: whether json formatter should emit default fields
   - include_text_separator optional: when protobuf string formatter is invoked to format multiple messages, all messages after the first one will be prefixed with character (0x1E)
-  - tls_client_cert optional: a chain of certificates to identify the caller, first certificate in the chain is considered as the leaf, followed by intermediates. Setting it enable mutual TLS authentication. Set the PEM content or the path to the PEM file.
+  - tls_client_cert optional: a chain of certificates to identify the caller, first certificate in the chain is considered as the leaf, followed by intermediates. Setting it enables mutual TLS authentication. Set the PEM content or the path to the PEM file.
   - tls_client_key optional: private key corresponding to the certificate. Set the PEM content or the path to the PEM file.
-  - tls_root_ca optional: defines additional root CAs to perform the call. can contains multiple CAs concatenated together. Set the PEM content or the path to the PEM file.
+  - tls_root_ca optional: defines additional root CAs to perform the call. Can contain multiple CAs concatenated together. Set the PEM content or the path to the PEM file.
   - ignore_verify_ssl optional: set to true if you use a self-signed SSL on remote for example
 ```
 

executors/http/README.md

@@ -1,6 +1,6 @@
 # Venom - Executor HTTP
 
-Step for execute a HTTP Request
+Step to execute an HTTP request
 
 ## Input
 In your yaml file, you can use:
@@ -23,9 +23,9 @@ In your yaml file, you can use:
   - no_follow_redirect (optional): indicates that you don't want to follow Location if server returns a Redirect (301/302/...)
   - skip_body: skip the body and bodyjson result
   - skip_headers: skip the headers result
-  - tls_client_cert (optional): a chain of certificates to identify the caller, first certificate in the chain is considered as the leaf, followed by intermediates. Setting it enable mutual TLS authentication. Set the PEM content or the path to the PEM file.
+  - tls_client_cert (optional): a chain of certificates to identify the caller, first certificate in the chain is considered as the leaf, followed by intermediates. Setting it enables mutual TLS authentication. Set the PEM content or the path to the PEM file.
   - tls_client_key (optional): private key corresponding to the certificate. Set the PEM content or the path to the PEM file.
-  - tls_root_ca (optional): defines additional root CAs to perform the call. Can contains multiple CAs concatenated together Set the PEM content or the path to the PEM file.
+  - tls_root_ca (optional): defines additional root CAs to perform the call. Can contain multiple CAs concatenated together. Set the PEM content or the path to the PEM file.
 
 ```
 
@@ -140,11 +140,11 @@ result.err
 JSON keys are lowercased automatically (eg. use `result.bodyjson.yourkey`, not
 `result.bodyjson.YourKey`).
 
-On top of that, if a JSON key contains special characters, they will be translate to underscores.
+On top of that, if a JSON key contains special characters, they will be translated to underscores.
 
 ### JSON arrays
 
-When a HTTP response contains a JSON array, you have to use following syntax
+When an HTTP response contains a JSON array, you have to use the following syntax
 to access specific key of an array: `result.bodyjson.array_name.array_name_index_in_array.key`
 
 Example if you want to get value of `path` key of *second* element in `apis` array: `result.bodyjson.apis.apis1.path`

executors/imap/README.md

@@ -27,7 +27,7 @@ As of today, these are the available commands:
 - **flag**: add, remove or set the flags of a mail
 - **move**: move a mail from one mailbox to another
 
-Multiple commands can be stated as once: they will be executed in the order they are presented under the `commands` field.
+Multiple commands can be stated at once: they will be executed in the order they are presented under the `commands` field.
 
 Each command consists of a `name` field which allows to specify the command to execute.
 Then they are composed of the `search` field and/or the `args` field.
@@ -170,8 +170,8 @@ commands:
 
 ### Assertions
 
-Each execution of a command produces a `result` Its content depends on the command and its execution.\
-Taking that multiple commands can be executed in a single testcase, the `result` object follows this syntax:
+Each execution of a command produces a `result`. Its content depends on the command and its execution.\
+Considering that multiple commands can be executed in a single testcase, the `result` object follows this syntax:
 ```json
 {
   "result": {
@@ -213,7 +213,7 @@ Where each command has its own results that can be asserted.
 As an example, here is a list of possible assertions after execution of two commands in the same testcase:
 ```yaml
 assertions:
-  # First ommand
+  # First command
   - result.commands.commands0.err ShouldBeEmpty
   # State of the mail before command execution (search)
   - result.commands.commands0.search.from ShouldEqual "from@mail-before-command-execution.com"