pytest-dev / pytest-dev/pytest-bdd

No substitution in --gherkin-terminal-reporter output for scenario outline in pytest parametrizing way

Open
#326 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.5k
Forks
251
Avg merge
43m
Merged PRs (30d)
2

Description

In issue 222 and 235, I saw the same issue was addressed if the scrnario outline is in traditional Gherkin way, i.e. via Examples in feature files. But if the parametrization is done via pytest way, see doc, and the output still does not substitute the in the output. like this:

pytest --disable-pytest-warnings --gherkin-terminal-reporter -k test_default_merge -vv
=========================================================================================================================== test session starts ============================================================================================================================
platform darwin -- Python 2.7.10, pytest-4.6.5, py-1.8.0, pluggy-0.12.0 -- /Users/murphy/Projects/pyocnos-IPI-integration-tests/venv/bin/python
cachedir: .pytest_cache
rootdir: /Users/murphy/Projects/pyocnos-IPI-integration-tests, inifile: tox.ini
plugins: bdd-3.2.1
collected 7 items / 5 deselected / 2 selected
Feature: applying a config to a switch should be idempotent, no matter it is a replace or merge
Scenario: default merge
Given switch <switch_name> has been alive
When replace its running config with <config_file_replacement>
....
(more output truncated)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with the shown pytest command and pytest parametrization pattern from the linked documentation. Trace the --gherkin-terminal-reporter output path and compare scenario-outline rendering for pytest parameters with the reported output; done means the parameter values replace the angle-bracket placeholders.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
40/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.