[m-dev.] Tests for Coverage Profiling.

Julien Fischer juliensf at csse.unimelb.edu.au
Thu Feb 21 14:19:18 AEDT 2008

On Thu, 21 Feb 2008, Paul Bone wrote:

> I've finished working on my coverage profiling change to the deep
> profilier, however I'd like to see the test suite test it.
> There doesn't appear to be anything specific to the deep profilier in
> the test suite.  I'm considering creating some tests and a framework for
> compiling a single-module program, running it, comparing the output to a
> .exp file, running mdprof_dump against the Deep.data file and checking
> it's output against a .deep_exp file.

That could be quite brittle depending on exactly what you propose
mdprof_dump should be printing.

> This will also have the affect of testing mdprof_dump, and any changes
> to mdprof_dump will require updating of tests.
> I can use some single module programs from general and hard_coded.  I
> may have to create my own to test the coverage profiling.
> Is this the best way to do this?  Any suggestions?

I suggest that you add a separate directory to tests, e.g.
tests/deep_profiler, that is only invoked when the test suite is run in
an a deep profiling grade.

mercury-developers mailing list
Post messages to:       mercury-developers at csse.unimelb.edu.au
Administrative Queries: owner-mercury-developers at csse.unimelb.edu.au
Subscriptions:          mercury-developers-request at csse.unimelb.edu.au

More information about the developers mailing list