On 21/09/2016 00:14, Neil Girdhar wrote:
As Ryan points out, pytest does this right. The way I understand it,
pytest is actively maintained and nose isn't. You should switch to
pytest as soon as possible.
Best,
Neil
Nose is no longer maintained but long live nose2
On Sun, Sep 18, 2016 at 02:52:31AM +0200, Arek Bulski wrote:
> I am using declarative testing a lot and I found out why unit tests are so
> clunky.
I don't think unit tests are clunky.
> The reason why assertEquals(a,b) is used is because if we put
> `assert a==b` then nose can catch the
As Ryan points out, pytest does this right. The way I understand it,
pytest is actively maintained and nose isn't. You should switch to pytest
as soon as possible.
Best,
Neil
On Saturday, September 17, 2016 at 8:55:43 PM UTC-4, Arek Bulski wrote:
>
> I am using declarative testing a lot and
Arek Bulski wrote:
def __glob_eq__(a,b):
if not a == b:
raise FoundInequalityError(a,b)
return True
assert obj1 == obj2 #<-- using eq above
How would you ensure that this overriding only applied in
the places you want it? You don't want to change the meaning
of == in the code
I am using declarative testing a lot and I found out why unit tests are so
clunky. The reason why assertEquals(a,b) is used is because if we put
`assert a==b` then nose can catch the AssertionError but wont find out what
was returned or expected. This could be easily overcome if we allow
