https://github.com/thiht/vscode-venom

Venom extension for Visual Studio Code
https://github.com/thiht/vscode-venom

venom visual-studio-code vscode vscode-extension

Last synced: 7 months ago
JSON representation

Venom extension for Visual Studio Code

• Host: GitHub
• URL: https://github.com/thiht/vscode-venom
• Owner: Thiht
• License: mit
• Created: 2022-02-17T21:35:29.000Z (over 3 years ago)
• Default Branch: master
• Last Pushed: 2024-08-21T12:33:04.000Z (10 months ago)
• Last Synced: 2024-08-21T13:55:15.184Z (10 months ago)
• Topics: venom, visual-studio-code, vscode, vscode-extension
• Language: TypeScript
• Homepage:
• Size: 4.29 MB
• Stars: 10
• Watchers: 3
• Forks: 2
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# vscode-venom

[![Visual Studio Marketplace Version](https://img.shields.io/visual-studio-marketplace/v/thiht.vscode-venom?color=0078d7&label=VS%20Marketplace)](https://marketplace.visualstudio.com/items?itemName=thiht.vscode-venom)

[![Open VSX Version](https://img.shields.io/open-vsx/v/thiht/vscode-venom?color=%23c160ef&label=Open%20VSX)](https://open-vsx.org/extension/thiht/vscode-venom)

[Venom](https://github.com/ovh/venom) integration with Visual Studio Code.

## Features

- Integration with Visual Studio Code's Testing workbench

![Screenshot showing Venom integration with the Testing workbench](./docs/testing-workbench.png)

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

![Screencast showing off Venom test suites autocomplete and validation](./docs/json-schema.gif)

- JSON/YAML schema for autocompleting and validating the [`.venomrc`](https://github.com/ovh/venom#use-a-configuration-file) configuration file

- Generate assertions from JSON

![Screencast showing off Venom assertions generation from a JSON](./docs/generate-assertions.gif)

## 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