New issue 695: pytest.mark.parameterize "fixture input not found"
https://bitbucket.org/pytest-dev/pytest/issue/695/pytestmarkparameterize-fixture-input-not
Alec Reiter:
I'm writing tests for a small library and I decided to use py.test after
hearing so many good things about it.
However, `pytest.mark.parameterize` is giving me some issues. At first, I
thought maybe I just mismatched some parens and it went off looking for a
fixture elsewhere. So I decided to start with the given example of parameterize:
@pytest.mark.parametrize("input,expected", [
("3+5", 8),
("2+4", 6),
("6*9", 42),
])
def test_eval(input, expected):
assert eval(input) == expected
But this gives the same error:
> fixture 'input' not found
>
> available fixtures: capfd, pytestconfig, recwarn, capsys, tmpdir, monkeypatch
>
> use 'py.test --fixtures [testpath]' for help on them.
I went off googling, but I couldn't find any answers that applied. Any ideas on
how to approach this?
I'm running Python 3.4.0 and py.test 2.6.4 inside of a virtualenv.
_______________________________________________
pytest-commit mailing list
pytest-commit@python.org
https://mail.python.org/mailman/listinfo/pytest-commit
