Skip to content

Releases: ovh/venom

v1.0.0-rc.2

10 Feb 08:46
2e76e0a
Compare
Choose a tag to compare

v1.0.0-rc.2

What's new?

This is a pre-release of venom 1.0.0. This release contains a lot of refactoring, bug fixes and new features since the release 0.28.0.

Command line arguments

Simplification of the command line options:

  • flags --log, --profiling were deleted. The flag -v was added. You can use -vv or -vvv to increase verbose.
  • flag --strict was deleted. If there is a test failure, venom will always exit with code 2.
  • flag --exclude was deleted. This can be easily replaced on command line with grep. Example: venom run $(ls *.yml|grep -v toexclude.yml).
  • flag --parallel was deleted. You can use parallel software in remplacement of the flag.
  • flag --no-check-variables was deleted, venom will always check variables.
  • flag --env was deleted. You can use --var or --var-from-file or .venomrc file to declare variables with value from environment variables. See https://github.com/ovh/venom#environment-variables. Notice that you can't use anymore FOO=bar venom run ..., you have now to use: VENOM_VAR_FOO=bar venom run ...

Options can be set with environment variables: VENOM_FORMAT=json venom run *.yml is the same as venom run --format=json *.yml.
See Readme for other flags usage.

Command line output

The output of venom command line was rewritten. It's much more readable with color and you can debug testsuite with a new keyword: info. See https://github.com/ovh/venom#debug-your-testsuites

Test variables

If you are using variables in your testsuite, it is recommended to declare them at the vars section of a testsuite. Then you have several options to set them. See https://github.com/ovh/venom#variables

Variable helpers

In this example, we will add simple quote around the .testA.myvariable.

- name: testB
  steps:
  - type: exec
    script: echo {{.testA.myvariable | squote}} > variable.with.simple.quote.txt
    assertions:
    - result.code ShouldEqual 0

See all variable helpers: https://github.com/ovh/venom#variable-helpers

Testsuite version

The version attribute in a testsuite was deleted. The version was used to control the basepath of the testsuite.
Venom now use as basepath the testsuite file, the same behaviour as version = "2" before.

This testsuite will read the file testa.json from the same directory as the testsuite itself.

name: Testsuite Read File
testcases:
- name: Testcase Read File
  steps:
  - type: readfile
    path: testa.json

Testcase name

If you have to write a reference to a testcase property, note that at runtime the testcase name is handled as a slug with uppercase support.

Skip testcase

It is possible to skip testcase according to some assertions. See https://github.com/ovh/venom#skip-testcase

Executors

A new executor is available: odbc. As this executor requires unixodbc driver, this is only available as plugin.

There is now three ways to write a venom executor: builtin, plugin or user-defined.

Plugin

Venom can now use .so plugin, the counterpart for using plugin is that you have to compile venom yourself.
.so files are not in the venom release.

User-defined executors

You can define reusable testcase as executor, and call it from your testsuite files.
Doc: https://github.com/ovh/venom#user-defined-executors

Compile, Test

A makefile is now available to build, test, etc.

$ make build
$ make plugins
$ make help # display all make commands

Changelog

Features

Bug Fixes

Refactoring

Read more

v1.0.0-rc.1

18 Jan 15:39
ae793f2
Compare
Choose a tag to compare

v1.0.0-rc.1

What's new?

This is a pre-release of venom 1.0.0. This release contains a lot of refactoring, bug fixes and new features since the release 0.28.0.

Command line arguments

Simplification of the command line options:

  • flags --log, --profiling were deleted. The flag -v was added. You can use -vv or -vvv to increase verbose.
  • flag --strict was deleted. If there is a test failure, venom will always exit with code 2.
  • flag --exclude was deleted. This can be easily replaced on command line with grep. Example: venom run $(ls *.yml|grep -v toexclude.yml).
  • flag --parallel was deleted. You can use parallel software in remplacement of the flag.
  • flag --no-check-variables was deleted, venom will always check variables.
  • flag --env was deleted. You can use --var or --var-from-file or .venomrc file to declare variables with value from environment variables. See https://github.com/ovh/venom#environment-variables. Notice that you can't use anymore FOO=bar venom run ..., you have now to use: VENOM_VAR_FOO=bar venom run ...

Options can be set with environment variables: VENOM_FORMAT=json venom run *.yml is the same as venom run --format=json *.yml.
See Readme for other flags usage.

Command line output

The output of venom command line was rewritten. It's much more readable with color and you can debug testsuite with a new keyword: info. See https://github.com/ovh/venom#debug-your-testsuites

Test variables

If you are using variables in your testsuite, it is recommended to declare them at the vars section of a testsuite. Then you have several options to set them. See https://github.com/ovh/venom#variables

Variable helpers

In this example, we will add simple quote around the .testA.myvariable.

- name: testB
  steps:
  - type: exec
    script: echo {{.testA.myvariable | squote}} > variable.with.simple.quote.txt
    assertions:
    - result.code ShouldEqual 0

See all variable helpers: https://github.com/ovh/venom#variable-helpers

Testsuite version

The version attribute in a testsuite was deleted. The version was used to control the basepath of the testsuite.
Venom now use as basepath the testsuite file, the same behaviour as version = "2" before.

This testsuite will read the file testa.json from the same directory as the testsuite itself.

name: Testsuite Read File
testcases:
- name: Testcase Read File
  steps:
  - type: readfile
    path: testa.json

Testcase name

If you have to write a reference to a testcase property, note that at runtime the testcase name is handled as a slug with uppercase support.

Skip testcase

It is possible to skip testcase according to some assertions. See https://github.com/ovh/venom#skip-testcase

Executors

A new executor is available: odbc. As this executor requires unixodbc driver, this is only available as plugin.

There is now three ways to write a venom executor: builtin, plugin or user-defined.

Plugin

Venom can now use .so plugin, the counterpart for using plugin is that you have to compile venom yourself.
.so files are not in the venom release.

User-defined executors

You can define reusable testcase as executor, and call it from your testsuite files.
Doc: https://github.com/ovh/venom#user-defined-executors

Compile, Test

A makefile is now available to build, test, etc.

$ make build
$ make plugins
$ make help # display all make commands

Changelog

Features

Bug Fixes

Refactoring

Read more

v1.0.0-beta.4

08 Jan 15:59
8d19a53
Compare
Choose a tag to compare

v1.0.0-beta.4

What's new?

This is a pre-release of venom 1.0.0. This release contains a lot of refactoring, bug fixes and new features since the release 0.28.0.

Command line arguments

Simplification of the command line options:

  • flags --log, --profiling were deleted. The flag -v was added. You can use -vv or -vvv to increase verbose.
  • flag --strict was deleted. If there is a test failure, venom will always exit with code 2.
  • flag --exclude was deleted. This can be easily replaced on command line with grep. Example: venom run $(ls *.yml|grep -v toexclude.yml).
  • flag --parallel was deleted. You can use parallel software in remplacement of the flag.
  • flag --no-check-variables was deleted, venom will always check variables.
  • flag --env was deleted. You can use --var or --var-from-file or .venomrc file to declare variables with value from environment variables. See https://github.com/ovh/venom#environment-variables. Notice that you can't use anymore FOO=bar venom run ..., you have now to use: VENOM_VAR_FOO=bar venom run ...

Options can be set with environment variables: VENOM_FORMAT=json venom run *.yml is the same as venom run --format=json *.yml.
See Readme for other flags usage.

Command line output

The output of venom command line was rewritten. It's much more readable with color and you can debug testsuite with a new keyword: info. See https://github.com/ovh/venom#debug-your-testsuites

Test variables

If you are using variables in your testsuite, it is recommended to declare them at the vars section of a testsuite. Then you have several options to set them. See https://github.com/ovh/venom#variables

Variable helpers

In this example, we will add simple quote around the .testA.myvariable.

- name: testB
  steps:
  - type: exec
    script: echo {{.testA.myvariable | squote}} > variable.with.simple.quote.txt
    assertions:
    - result.code ShouldEqual 0

See all variable helpers: https://github.com/ovh/venom#variable-helpers

Testsuite version

The version attribute in a testsuite was deleted. The version was used to control the basepath of the testsuite.
Venom now use as basepath the testsuite file, the same behaviour as version = "2" before.

This testsuite will read the file testa.json from the same directory as the testsuite itself.

name: Testsuite Read File
testcases:
- name: Testcase Read File
  steps:
  - type: readfile
    path: testa.json

Testcase name

If you have to write a reference to a testcase property, note that at runtime the testcase name is handled as a slug with uppercase support.

Skip testcase

It is possible to skip testcase according to some assertions. See https://github.com/ovh/venom#skip-testcase

Executors

A new executor is available: odbc. As this executor requires unixodbc driver, this is only available as plugin.

There is now three ways to write a venom executor: builtin, plugin or user-defined.

Plugin

Venom can now use .so plugin, the counterpart for using plugin is that you have to compile venom yourself.
.so files are not in the venom release.

User-defined executors

You can define reusable testcase as executor, and call it from your testsuite files.
Doc: https://github.com/ovh/venom#user-defined-executors

Compile, Test

A makefile is now available to build, test, etc.

$ make build
$ make plugins
$ make help # display all make commands

Changelog

Features

Bug Fixes

Refactoring

Read more

v1.0.0-beta.2

30 Nov 15:10
3adefcc
Compare
Choose a tag to compare

v1.0.0-beta.2

What's new?

This is a pre-release of venom 1.0.0. This release contains a lot of refactoring, bug fixes and new features since the release 0.28.0.

Command line arguments

Simplification of the command line options:

  • flags --log, --profiling were deleted. The flag -v was added. You can use -vv or -vvv to increase verbose.
  • flag --strict was deleted. If there is a test failure, venom will always exit with code 2.
  • flag --exclude was deleted. This can be easily replaced on command line with grep. Example: venom run $(ls *.yml|grep -v toexclude.yml).
  • flag --parallel was deleted. You can use parallel software in remplacement of the flag.
  • flag --no-check-variables was deleted, venom will always check variables.
  • flag --env was deleted. You can use --var or --var-from-file or .venomrc file to declare variables with value from environment variables. See https://github.com/ovh/venom#environment-variables. Notice that you can't use anymore FOO=bar venom run ..., you have now to use: VENOM_VAR_FOO=bar venom run ...

Options can be set with environment variables: VENOM_FORMAT=json venom run *.yml is the same as venom run --format=json *.yml.
See Readme for other flags usage.

Command line output

The output of venom command line was rewritten. It's much more readable with color and you can debug testsuite with a new keyword: info. See https://github.com/ovh/venom#debug-your-testsuites

Test variables

If you are using variables in your testsuite, it is recommended to declare them at the vars section of a testsuite. Then you have several options to set them. See https://github.com/ovh/venom#variables

Variable helpers

In this example, we will add simple quote around the .testA.myvariable.

- name: testB
  steps:
  - type: exec
    script: echo {{.testA.myvariable | squote}} > variable.with.simple.quote.txt
    assertions:
    - result.code ShouldEqual 0

See all variable helpers: https://github.com/ovh/venom#variable-helpers

Testsuite version

The version attribute in a testsuite was deleted. The version was used to control the basepath of the testsuite.
Venom now use as basepath the testsuite file, the same behaviour as version = "2" before.

This testsuite will read the file testa.json from the same directory as the testsuite itself.

name: Testsuite Read File
testcases:
- name: Testcase Read File
  steps:
  - type: readfile
    path: testa.json

Testcase name

If you have to write a reference to a testcase property, note that at runtime the testcase name is handled as a slug with uppercase support.

Skip testcase

It is possible to skip testcase according to some assertions. See https://github.com/ovh/venom#skip-testcase

Executors

A new executor is available: odbc. As this executor requires unixodbc driver, this is only available as plugin.

There is now three ways to write a venom executor: builtin, plugin or user-defined.

Plugin

Venom can now use .so plugin, the counterpart for using plugin is that you have to compile venom yourself.
.so files are not in the venom release.

User-defined executors

You can define reusable testcase as executor, and call it from your testsuite files.
Doc: https://github.com/ovh/venom#user-defined-executors

Compile, Test

A makefile is now available to build, test, etc.

$ make build
$ make plugins
$ make help # display all make commands

Changelog

Features

Bug Fixes

Refactoring

Read more

v1.0.0-beta.1

26 Nov 13:32
9eb3367
Compare
Choose a tag to compare

v1.0.0-beta

24 Nov 08:56
8eff13c
Compare
Choose a tag to compare

v0.28.0

07 Oct 12:49
b349e3a
Compare
Choose a tag to compare

(2020-10-07)

Features

  • cli: allow multiple occurence of --var-from-file (#247) (0d2ed76), closes #247
  • context/web: add prefs for chromedriver (#257) (#258) (749a51c), closes #257 #258
  • dbfixtures: add skipResetSequences parameter (c1d7719)
  • executor/http: added http debug infos in http executor (#259) (dc7ae07), closes #259
  • executor/web: Add text and value attribute in result of test step (#227) (19b6f1a), closes #227
  • executor/web: add gecko web driver (#225) (c9c106c), closes #225
  • executor/web: add statement to manage select component (#229) (9a166c8), closes #229
  • executor/web: add statement to upload file (#232) (9d5460b), closes #232
  • executor/web: add statements to manage popup actions (#230) (cce97ad), closes #230
  • executor/web: implement next window (#226) (e4ba258), closes #226
  • executor/web: statement to manage browser history actions (#237) (24e4e6c), closes #237
  • http: read proxy from environment (#251) (62a00a9), closes #251
  • testfixtures: upgrade testfixtures to v3 (3686985)

Bug Fixes

  • cli: don't iterate over empty varFiles (#255) (55f457d), closes #255
  • cli: give higher priority to --var over --var-from-file (#246) (50fdc39), closes #246
  • executor/http: save multiple set-cookie headers when returned by the server (#266) (f9547b9), closes #266
  • executor/http: support setting host in headers (#218) (e145c61), closes #218
  • executor/web: add statements to manage frame (#228) (07c6ecd), closes #228
  • executor/web: merge conflicts (11570d7)
  • cli: do not truncate filename in results (#273) (b349e3a), closes #273 #254
  • test: fix some http asserts (#272) (941af31), closes #272

Documentation

v0.27.0

27 Nov 14:53
c23909e
Compare
Choose a tag to compare

0.27.0 (2019-11-27)

Features

Bug Fixes

0.26.0

17 Jun 12:18
Compare
Choose a tag to compare

0.26.0 (2019-06-15)

Features

Bug Fixes

v0.25.0

28 Feb 16:51
Compare
Choose a tag to compare

0.25.0 (2019-02-28)

Features

  • Dependencies updates