On Thu, 2018-03-22 at 06:07 -0700, buddha wrote:
> Self promotion moment, I wrote Charcoal to do basic unit testing in
> Chapel.  It would be great if you want to provide feedback: https://g
> ithub.com/buddha314/Charcoal <https://github.com/buddha314/Charcoal>
> It’s pretty early, I’d use the develop branch.  We use it extensively
> in our internal tools.  Otherwise, the internal team uses
> “start_test” which is hard to find the docs for and right now I
> can’t.
> 

I shall give it a whirl.

At the risk of "statin' the bleedin' obvious":

Property-based testing is now as important as example-based testing. So
in the Python world, Hypothesis is now as important for testing as
pytest. In the C++ world there is RapidCheck for property-based testing
as well as Catch2 for example-based testing – though Catch2 may well do
something in the RapidCheck style, in the same way that ScalaTest
(example-based) can make use of ScalaCheck (property-based) in an
integrated way. QuickCheck from Haskell is the iconic property-based
framework for many people.  Hence there is a Rust QuickCheck, but there
are others for Rust as well.

I'd suggest the right strategy for Chapel would be to have a testing
framework that supports property-based testing as well as example-based 
testing. Also trying to avoid inheritance might be a good move, pytest
uses a runtime infrastructure rather than unittest's inheritance based
structure and many people find it much more flexible and usable.

And shrinking is a critical feature of property-based testing.
 
-- 
Russel.
===========================================
Dr Russel Winder      t: +44 20 7585 2200
41 Buckmaster Road    m: +44 7770 465 077
London SW11 1EN, UK   w: www.russel.org.uk

Attachment: signature.asc
Description: This is a digitally signed message part

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Chapel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-users

Reply via email to