Thomas Davie gmail.com> writes:
> On 1 Aug 2008, at 16:01, Roberto D'Aprile wrote:
>
> > Hello to everybody
> >
> > I'm using haskell for some research work and now i need to evaluate
> > the performance of some simple haskell programs in particular
> > information on the like, CPU cycles, b
the package author need only run:
$ ./Setup configure
$ ./Setup build
$ ./Setup test
to produce a file detailing the results of the test suite.
I apologize for taking up your time with a such a lengthy message, and
eagerly await your feedback!
Thanks!
--
Thomas Tuegel
[1] http://hackage
On Thu, Apr 1, 2010 at 9:13 PM, Rogan Creswick wrote:
> On Thu, Apr 1, 2010 at 3:52 PM, Thomas Tuegel wrote:
> There are a few frameworks that provide limited degrees of this
> functionality. I've recently added to test-framework so that the
> results can be gathered into a
see where their packages are failing. Certainly, any
single package author could write a tool to do this for any single
package's tests, but now we have a common tool everyone can use simply
by writing tests.
To summarize: everyone's life is easier if we do this bit of plumbing for them.
--
Thomas Tuegel
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
is
very helpful!
Thanks!
--
Thomas Tuegel
Throughout this proposal, examples are given to indicate how a package
author would utilize the features proposed here. In all these
examples, suppose that the programmer is the author of the
'haskell-foo' package, which exposes the module
r a proper 'Test' stanza in the package description file and leave
it at that?
Thanks!
--
Thomas Tuegel
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
or this proposal, it's all tangential.)
> See my comments about running multiple test suites, and parameterized
> test suites above. I think richer parameters are necessary.
> (possibly just a --pass-through flag that hands all the subsequent
> parameters off to the test executable(s))
That is an excellent suggestion that I will definitely adopt in my
eventual proposal.
Thanks!
--
Thomas Tuegel
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
I apologize for spamming, but it only just occurred to me how to get
the best aspects of both our ideas:
On Tue, Apr 6, 2010 at 8:28 PM, Thomas Tuegel wrote:
> On Tue, Apr 6, 2010 at 7:43 PM, Rogan Creswick wrote:
>> The existing Executable sections may serve the need fine, if
executables get
cut from the PackageDescription. Am I missing something?
--
Thomas Tuegel
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
hackage test agents) and convert to other formats (e.g.
> integration in companies in-house systems).
Rogan mentioned possible upcoming support in test-framework for JUnit
XML as an output format for test results. That certainly seems to be
widely supported; do you think it is suitable?
--
Thomas Tuegel
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
and/or pointers, I'd love to hear
them!
Thanks!
--
Thomas Tuegel
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
read my
proposal at the GSoC site, but the proposal submission form kinda
mangled my formatting. There is a public Google Documents version of
my proposal at
https://docs.google.com/Doc?docid=0AZzNFnSY9FOeZGd6MnQ4cWNfM2Q2N2J0OWZn&hl=en
which should be up-to-date and contain al
test
result data structure?
> As you suggest in your other post, it would make sense to adapt
> test-framework to implement the interface specified by Cabal.
I agree, as well; this is essentially the approach I took in my proposal.
--
Thomas Tuegel
__
ir tests, they
can give them independent test stanzas in the .cabal file. Either
they put the tests in different executables, or the test framework can
provide command-line options for turning tests on and off.
Those are the big two usage scenarios we've discussed for the
own bug. A patch is available, so it should be fixed in
the next version.
--
Thomas Tuegel
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
e to put any
flag gymnastics in your .cabal file.
If this doesn't work for you, please let me know, because it's a bug.
Thanks!
--
Thomas Tuegel
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
On Wed, Feb 8, 2012 at 4:42 AM, Christoph Breitkopf
wrote:
> Hello Thomas,
>
> On Wed, Feb 8, 2012 at 4:03 AM, Thomas Tuegel wrote:
>>
>> First, as author of the test suite code, let me apologize for the
>> terrible documentation.
>>
>> This is absolutely N
17 matches
Mail list logo