All issues

Search results

Authoring Feature file with steps that exist in a dependency library

Status: Open.

#77 In jimasp/behave-vsc;

· dhartford opened on Feb 12, 2026

No JUnit file was written for this test error after moving features to another location

Status: Open.

#76 In jimasp/behave-vsc;

· afoalb opened on Jan 20, 2026

Can't download vscode to run tests

Status: Open.

#74 In jimasp/behave-vsc;

· gabeseltzer opened on Oct 24, 2025

Debug with custom config in launch.json

Status: Open.

#72 In jimasp/behave-vsc;

· gabeseltzer opened on Oct 22, 2025

Error for duplicate scenarios is intrusive

Status: Open.

#70 In jimasp/behave-vsc;

· gabeseltzer opened on Oct 22, 2025

Step autocomplete in feature files leads to duplicated text in the step

Status: Open.

#68 In jimasp/behave-vsc;

· gabeseltzer opened on Oct 20, 2025

Add a DefinitionProvider for .feature files

Status: Open.

#66 In jimasp/behave-vsc;

· gabeseltzer opened on Oct 20, 2025

Re-opening issue #61 Unexpected scheme: chat-editing-text-model

Status: Open.

#65 In jimasp/behave-vsc;

· mikej100 opened on Sep 1, 2025

Behave v1.3.0 introduces a split between "Error" and "Failure" outcome which is not handled by junitparser

Status: Open.

#64 In jimasp/behave-vsc;

· victor-eh opened on Aug 13, 2025

User Setting for cli arguments to send to behave

feature requestNew feature or new functionality requestNew feature or new functionality request

Status: Open.

#60 In jimasp/behave-vsc;

· gabeseltzer opened on Mar 13, 2025

Submit extension to Open VSX Registry (Codium)

Status: Open.

#58 In jimasp/behave-vsc;

· bittner opened on Dec 3, 2024

Support alternate step parsers (re in particular)

Status: Open.

#57 In jimasp/behave-vsc;

· gabeseltzer opened on Dec 3, 2024