[Pytest-commit] commit/pytest: hpk42: is actually a new feature, the syntax: pytest.mark.parametrize("arg1, arg2", ...)

[commits-noreply at bitbucket.org]

1 new commit in pytest:

https://bitbucket.org/hpk42/pytest/commits/a9bfa2e8b08d/
Changeset:   a9bfa2e8b08d
User:        hpk42
Date:        2013-09-27 14:15:53
Summary:     is actually a new feature, the syntax: pytest.mark.parametrize("arg1,arg2", ...)
Affected #:  1 file

diff -r 05ab108a29e7a9fdfb295b133ad077d622f7a21f -r a9bfa2e8b08d7db4f2d68a63dcf80441666fe818 CHANGELOG
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -52,6 +52,12 @@
   don't run teardownX.  This internally introduces a new method "node.addfinalizer()"
   helper which can only be called during the setup phase of a node.
 
+- simplify pytest.mark.parametrize() signature: allow to pass a CSV-separated string 
+  to specify argnames.  For example: 
+  ``pytest.mark.parametrize("input,expected",  [(1,2), (2,3)])``
+  works as well as the previous:
+  ``pytest.mark.parametrize(("input", "expected"), ...)``.
+
 - add support for setUpModule/tearDownModule detection, thanks Brian Okken.
 
 - integrate tab-completion on options through use of "argcomplete".
@@ -114,10 +120,6 @@
 
 - fix issue316 - properly reference collection hooks in docs
 
-- simplify parametrize() signature: allow to pass a CSV-separated string 
-  to specify argnames.  For example: ``pytest.mark.parametrize("input,expected",  [(1,2), (2,3)])`` is possible now in addition to the prior
-  ``pytest.mark.parametrize(("input", "expected"), ...)``.
-
 - fix issue 306 - cleanup of -k/-m options to only match markers/test
   names/keywords respectively.  Thanks Wouter van Ackooy.

Repository URL: https://bitbucket.org/hpk42/pytest/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.