thiht/vscode-venom

Venom extension for Visual Studio Code

vscode-venom

Venom integration with Visual Studio Code.

Features

• Integration with Visual Studio Code's Testing workbench

• JSON/YAML schema for autocompleting and validating the test suites

• JSON/YAML schema for autocompleting and validating the .venomrc configuration file
• Generate assertions from JSON

Caveats

• Only Venom > 1.0.0 is supported
• Test suites must be named as *.venom.yml, otherwise the extension will not be activated
• The JSON schema case is strict, so for example you have to use bodyFile instead if bodyfile in the http executor

vscode-venom's Issues

feat: add support of executor ovhapi

Missing support of ovhapi executor
Error on VScode and suggest HTTP steps in replacement

bug: if verbosity > 1 unexpected venom output

Hello,

It the verbosity level is upper than 1, extension can't deal with multiple files from output.

here it's because verbosity is set into the .venomrc

Regards,

User executors release broke core executors autocompleting

Issue: Autocomplete Not Working for User Executor in v1.7.0
v1.7.0 - #7

Steps to Reproduce:

1. Create a user executor and a testsuite.venom.yml file.
2. Add a test case with the type set to the new user executor.

Expected Behavior: Autocomplete should display the executor.
Actual Behavior: No autocomplete suggestions are available.

I attempted disabling and re-enabling the plugin. While it loads, it initially throws IntelliSense errors. However, these errors disappear when I type a new line.

feat: venom has fixed a problem with casing preserving

As of ovh/venom#709 a fix was provided to preserve casing. This affects this plugin as we lower case when converting json payload to result.bodyjson

e.g.

{
   "data": {
    "firstName": "firstName"
}

gets converted to

- result.bodyjson.data.firstname ShouldEqual "firstName"

update required to keep casing and produce

- result.bodyjson.data.firstName ShouldEqual "firstName"

bug: variables and variables_files ignore from .venomrc

Hello,

If I declare some variables_files in .venomrc like:

variables_files:
  - ovh_api.yaml

there are not take in account during Run Test

Error message:
unknown endpoint '', consider checking 'Endpoints' list of using an URL

If I declare on top of test file:

vars:
  ovh.endpoint: 'ovh-eu'

Error message change to:
missing application key, please check your configuration or consult the documentation to create one

Content of ovh_api.yaml:

ovh.endpoint: 'ovh-eu'
ovh.applicationKey: xxxx
ovh.applicationSecret: xxxx
ovh.consumerKey: xxxx

If I run venom from shell, no error.

Same if I set variable directly:

variables: 
  - ovh.endpoint='ovh-eu'
  - ovh.applicationKey=xxxx
  - ovh.applicationSecret=xxxx
  - ovh.consumerKey=xxxx

Regards,

feat: add support to register into venom.schema.json user defined executors

testcases:
  - name: get_login_token
    steps:
    - type: get_login_token

Since this type is not present in the venom.schema.json we get an error in the editor

user defined executors is a common functionality used to avoid duplicate code. To have the plugin register the defined types in lib directory defined in the .venomrc would be really useful

Definition of the user defined executor:

executor: get_login_token
input:
  arg: {}
steps:
  - script: sh ../../resources/scripts/gettoken.sh
    
output: 
   token: "{{.result.systemout}}"