On 02/15/2011 10:00 AM, Lars T. Kyllingstad wrote:
On Sun, 13 Feb 2011 23:03:06 +0100, spir wrote:
1. Named unittests allowing test suites in the form of (just an
example):
unittest test1 {
...
}
unittest test2 {
...
}
unittest test3 {
...
}
unittest {
test1;
test
On Sun, 13 Feb 2011 23:03:06 +0100, spir wrote:
> 1. Named unittests allowing test suites in the form of (just an
> example):
>
> unittest test1 {
> ...
> }
> unittest test2 {
> ...
> }
> unittest test3 {
> ...
> }
> unittest {
> test1;
> test2;
> test3;
> }
>
> /Un
On Tuesday 15 February 2011 00:46:25 spir wrote:
> On 02/15/2011 02:42 AM, Jonathan M Davis wrote:
> > On Monday, February 14, 2011 17:26:26 Don wrote:
> >> Jonathan M Davis wrote:
> >>> On Monday, February 14, 2011 12:49:11 Tomek Sowiński wrote:
> spir napisał:
> > * Why isn't testList a
On 02/15/2011 02:42 AM, Jonathan M Davis wrote:
On Monday, February 14, 2011 17:26:26 Don wrote:
Jonathan M Davis wrote:
On Monday, February 14, 2011 12:49:11 Tomek Sowiński wrote:
spir napisał:
* Why isn't testList a unittest block?
Using named funcs, I can switch on& off specific test sui
On Monday, February 14, 2011 17:26:26 Don wrote:
> Jonathan M Davis wrote:
> > On Monday, February 14, 2011 12:49:11 Tomek Sowiński wrote:
> >> spir napisał:
> >>> * Why isn't testList a unittest block?
> >>>
> >>> Using named funcs, I can switch on & off specific test suites by
> >>> (un)commenti
Jonathan M Davis wrote:
On Monday, February 14, 2011 12:49:11 Tomek Sowiński wrote:
spir napisał:
* Why isn't testList a unittest block?
Using named funcs, I can switch on & off specific test suites by
(un)commenting their call from the main and unique unittest block. Else,
either they all run
On Monday, February 14, 2011 12:49:11 Tomek Sowiński wrote:
> spir napisał:
> > * Why isn't testList a unittest block?
> >
> > Using named funcs, I can switch on & off specific test suites by
> > (un)commenting their call from the main and unique unittest block. Else,
> > either they all run, or n
On 02/14/2011 09:49 PM, Tomek Sowiński wrote:
spir napisał:
* Why isn't testList a unittest block?
Using named funcs, I can switch on& off specific test suites by (un)commenting
their call from the main and unique unittest block. Else, either they all run,
or none. During development, I only
spir napisał:
> * Why isn't testList a unittest block?
>
> Using named funcs, I can switch on & off specific test suites by
> (un)commenting
> their call from the main and unique unittest block. Else, either they all
> run,
> or none. During development, I only keep active the test func(s) re
Hello,
Back to the subject of using unittest and assert. I'll try to illustrate a
testing style that seems to be rare in the D community, is not properly
supported by D builtin tools --while this would require only minimal
improvements--, and is imo rather sensible, practicle and efficient. U
10 matches
Mail list logo
