Hello,
my name is Philipp Konrad, I am a computer science student, a young Python
programmer and researcher from Vienna, Austria.
My developer experience started around two years ago in Java, but half year
ago I was introduced to the Python world.
I want to contribute to the py or py.test project
Hello Philipp,
On Mon, Nov 19, 2012 at 12:41 +0100, Philipp Konrad wrote:
Hello,
my name is Philipp Konrad, I am a computer science student, a young Python
programmer and researcher from Vienna, Austria.
welcome!
My developer experience started around two years ago in Java, but half year
Hello Holger,
- Do you have experience in some form of automated testing? Have you
played with nose, unittest? Played with pytest itself?
Regularly I use unittest and basic applications of pytest. So far, I
never have used nose.
- are you familiar with mercurial or git? Bitbucket.org?
No,
On Mon, Nov 19, 2012 at 14:54 +0100, Philipp Konrad wrote:
Hello Holger,
- Do you have experience in some form of automated testing? Have you
played with nose, unittest? Played with pytest itself?
Regularly I use unittest and basic applications of pytest. So far, I
never have used nose.
Hi folks,
while writing tests on a new project using pytest-2.3 i noticed again an
inconvience: fixtures such as tmpdir or monkeypatch could implementation-wise
easily support being called from non-function scoped fixtures. But
currently if you do::
@pytest.fixture(scope=module)
def
On Mon, Nov 19, 2012 at 21:53 +, Floris Bruynooghe wrote:
@pytest.fixture(scope=any)
def monkeypatch(...):
# unmodified builtin monkeypatch implementation
@pytest.fixture(scope=module)
def something(monkeypatch):
...
This would not raise a
On Mon, Nov 19, 2012 at 22:04 +, holger krekel wrote:
the one in ``something(monkeypatch)`` above. monkeypatch-finalizers
would raher be called after a test function using the other
fixture has finalized. I am not sure if there is confusion potential
about this.
For
