Re: [myhdl-list] Pythonic Test frameworks

[Christopher F. <chr...@gm...>]

On 11/8/11 9:01 PM, Christopher Felton wrote:
> On 11/8/11 7:04 PM, Bob Cunningham wrote:
>> On 11/07/2011 08:07 PM, Christopher Felton wrote:
>>> On 11/7/11 7:21 PM, Bob Cunningham wrote:
>>>> FWIW, py.test seems to be the way MyHDL itself is going...
>>>>
>>>> -BobC
>>> ...
>>>
>>> The following, http://bit.ly/sc3vrI, is a brief mention of py.test used
>>> instead of unittest (from a couple years ago) from the myhdl-list.
>>>
>>> But I do believe py.test is limited.  If you are ok writing with only
>>> simple asserts, I believe py.test is ok.  But unittest supports more
>>> advanced features, automatically verify raised exceptions (continue if
>>> raised fail if not).
>>>
>>> I guess an argument against py.test, is that it is another package that
>>> needs to be installed.  Where as, unittest is part of the standard
>>> Python library, hmmm.
>>>
>>> Regards,
>>> Chris
>>
>> Well, MyHDL is, itself, "another package that needs to be installed"!
>>
>> See the end of this page: http://www.myhdl.org/doku.php/cookbook:stopwatch
>
> Thanks for the reminder, this is a good commentary on py.test versus
> unittest.  This is a good read for anyone trying to determine which test
> framework to use.

I think this is the important quote from the py.test commentary at the 
end of the stopwatch example.

"""
However, I believe that the benefits are far more important than the 
disadvantages. Moreover, some disadvantages may disappear over time. 
Consequently, I plan to promote py.test as the unit testing framework of 
choice for MyHDL in the future.
"""

I don't think anything has changed since this was posted.

Regards,
Chris