On these mason-related topics, I just wanted to mention that Sam Partee,
the intern who drafted mason last summer, will be returning to Cray this
summer and, barring surprises, will likely be beefing up mason support and
features.
-Brad
On Thu, 22 Mar 2018, Ben Albrecht wrote:
Hi Russel,
Mason test functionality is in the Mason roadmap[1]. However, as Brian notes,
we currently do not have a user-facing test framework, so that is somewhat of a
prerequisite to mason test functionality.
Demand for a test framework has ramped up significantly over the past few
months, so I hope to see a language-provided solution prioritized soon. As
Brian has mentioned, many users currently use Chapel's internal test framework,
which is documented in the developer documentation[2], and also the more recent
community-developed Charcoal library. I have not personally had any experience
with Charcoal yet, but I am supportive of the effort.
Thanks,
~ben
[1] https://github.com/chapel-lang/chapel/issues/7106
[2]
https://github.com/chapel-lang/chapel/blob/master/doc/rst/developer/bestPractices/TestSystem.rst
________________________________
From: Russel Winder <[email protected]>
Sent: Thursday, March 22, 2018 6:33:50 AM
To: Chapel_Users
Subject: Mason and testing
Hi,
|> mason test
error: no such subcommand
Uuuuurrrrrr… so Chapel programmers don't write tests?
yours
Upset of Clapham Junction
--
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<http://www.russel.org.uk>
------------------------------------------------------------------------------
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
