issues
search
jimasp
/
behave-vsc
A vscode extension that provides a test runner/debugger and navigation for Python behave tests
https://marketplace.visualstudio.com/items?itemName=jimasp.behave-vsc
Other
15
stars
3
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Indent is tab instead of spaces
#51
maeddlae
opened
3 weeks ago
1
Triple-quoted strings are marked as comments in the gherkin grammar file
#50
WorldEnd-Formatting
opened
1 month ago
1
Official Release
#49
schwaerz
opened
2 months ago
1
No JUnit file was written for this test. Check output in Behave VSC output window.
#48
thedayofcondor
closed
3 months ago
9
Run test with admin privileges
#47
andi-h
closed
4 months ago
1
Ability to switch command used to run behave.
#46
destos
opened
6 months ago
1
[Feature request] Setting breakpoints at the steps in the feature files
#45
chengwei45254
closed
8 months ago
2
Scenarios names with <variable> of a scenario outline show <variable> in the test explorer
#44
kappa10j
closed
8 months ago
2
0.6.4
#43
jimasp
closed
8 months ago
0
0.6.4
#42
jimasp
closed
8 months ago
0
Behave vsc 0.6.3
#41
jimasp
closed
8 months ago
0
0.6.3
#40
jimasp
closed
8 months ago
0
Add ability to change CWD
#39
konradzagozda
closed
8 months ago
10
0.6.2
#38
jimasp
closed
8 months ago
0
Configurable steps folder
#37
kconkas
closed
8 months ago
13
Problem with multi-line scenario name
#36
dmateja
closed
9 months ago
2
0.6.1
#35
jimasp
closed
9 months ago
0
0.6.0 does not run a scenario if more than one scenario in a feture file and there are double quotes in the scenario title
#34
chengwei45254
closed
9 months ago
2
Run/Debug config
#33
pespinel
closed
9 months ago
1
Tests running in parallel despite `runParallel` = `false`
#32
schwaerz
closed
9 months ago
3
${workspaceFolder} in behave settings.json does not get resolved when running w/o debugger
#31
schwaerz
closed
11 months ago
3
Output window support color
#30
g199209
closed
11 months ago
1
0.6.0
#29
jimasp
closed
1 year ago
0
Feature file outline in VS Code outline view
#28
tschroeder13
opened
1 year ago
0
Feature/build fix
#27
KCarrascoB
closed
1 year ago
0
Bug in step detection
#26
klausmyrseth
closed
1 year ago
1
Change the test command to work with behave-django
#25
star-jay
closed
1 year ago
2
0.5.0
#24
jimasp
closed
1 year ago
0
Can running a feature test invokes just one test run command?
#23
chengwei45254
closed
1 year ago
14
Hotfix
#22
jimasp
closed
1 year ago
0
Add examples in test panel tree view
#21
alexvaut
opened
1 year ago
6
Hotfix - scenario outline with parameter + new debug stop detection
#20
jimasp
closed
1 year ago
0
Support for Scenario Outline
#19
schwaerz
closed
1 year ago
4
Initial release?
#18
mike-oakley
closed
1 year ago
2
Test Status Displays Failed when test passes
#17
nls-jsiscaretti
closed
1 year ago
1
Bump terser from 5.12.1 to 5.14.2
#16
dependabot[bot]
closed
1 year ago
0
"No module named 'features'" for `features` folder that is not in root
#15
ycsin
closed
1 year ago
2
Step References
#14
jimasp
closed
2 years ago
0
quick fix for envVarList deprecation warning text
#13
jimasp
closed
2 years ago
0
Allow passing environment variables from workspace
#12
mike-oakley
closed
2 years ago
5
multiroot support, and switch to junit
#11
jimasp
closed
2 years ago
0
Run all from feature file and extra path checks
#10
jimasp
closed
2 years ago
0
justMyCode
#9
jimasp
closed
2 years ago
0
Custom feature paths, handle file rename better, event logging for all event hooks
#8
jimasp
closed
2 years ago
0
Parse buffer
#7
jimasp
closed
2 years ago
0
handle hook errors and debug stop
#6
jimasp
closed
2 years ago
0
quick fix for env var list
#5
jimasp
closed
2 years ago
0
Settings list fix
#4
jimasp
closed
2 years ago
0
env var setting and various minor fixes
#3
jimasp
closed
2 years ago
0
Go to step def fix
#2
jimasp
closed
2 years ago
0
Next