[m-users.] Automated testing of Mercury code

[Wim Vanhoof]

Hi Ben,

The work was indeed not continued after graduation of my former PhD student (François Degrave). The code was mainly written by Peter Biener but will most likely not have been updated for a few years.

As for myself, the subject still interests me but I am currently lacking the manpower to continue that work, so feel free to fix whatever it Is you can/are interested to fix!

Best,

Wim




> Op 28 sep. 2018, om 00:41 heeft Benjamin Schmidt <benjamin.schmidt at alumni.unimelb.edu.au> het volgende geschreven:
> 
> Hi!
> 
> I'm enjoying reviving my interest in Mercury at the moment.
> 
> I'm wondering if you know or are associated with any test frameworks for Mercury?
> 
> I came across this:
> 
> https://sourceforge.net/projects/mercurytest/
> 
> which is related to this paper:
> 
> https://arxiv.org/abs/1009.3765
> 
> but it seems to have gone stale (not compatible with the current release of the day, I suspect due to changes in the standard library). I'll probably see if I can fix it, but thought I'd ask as well, just in case you know of anything else.
> 
> I'm aware, of course, of hand-written tests in the compiler and other projects, but more ready-to-use tooling is of great benefit to the productive developer, so I'm interested in what's available in that space.
> 
> (I'm also interested in https://github.com/stewy33/hophacks2018 for the same reason but haven't had much chance to delve into it yet.)
> 
> Smiles.
> 
> Ben
> 
> 
> 
> _______________________________________________
> users mailing list
> users at lists.mercurylang.org
> https://lists.mercurylang.org/listinfo/users