This post marks the start of the two week review process of std.experimental.testing.

PR: https://github.com/D-Programming-Language/phobos/pull/3207
Dub: http://code.dlang.org/packages/unit-threaded
Doc: See CyberShadow/DAutoTest for up-to-date documentation build

Previous Thread: http://forum.dlang.org/post/uzocokshugchescbawlj@forum.dlang.org

On Wednesday, 9 September 2015 at 15:20:41 UTC, Robert burner Schadek wrote:
> This post marks the start of the two week review process of std.experimental.testing.
>
> PR: https://github.com/D-Programming-Language/phobos/pull/3207
> Dub: http://code.dlang.org/packages/unit-threaded
> Doc: See CyberShadow/DAutoTest for up-to-date documentation build
>
> Previous Thread: http://forum.dlang.org/post/uzocokshugchescbawlj@forum.dlang.org

Package-level documentation seems to be missing from the auto-generated documentation.

The gen_ut_main link on the side bar is also a 404.

std.experimental.testing.options.Options and std.experimental.testing.reflection.TestData fields have no DDoc, so they don't show up in the generated documentation.

Is there going to be a shouldEqual that's specialized for floating point, or should shouldBeTrue(approxEqual(...)) be used instead? (If so, this should be documented)

std.experimental.testing.testcase.TestCase.numTestsRun should be @property?

On Wednesday, 9 September 2015 at 18:54:30 UTC, Brian Schott wrote:
> On Wednesday, 9 September 2015 at 15:20:41 UTC, Robert burner Schadek wrote:
>> This post marks the start of the two week review process of std.experimental.testing.
>>
>> PR: https://github.com/D-Programming-Language/phobos/pull/3207
>> Dub: http://code.dlang.org/packages/unit-threaded
>> Doc: See CyberShadow/DAutoTest for up-to-date documentation build
>>
>> Previous Thread: http://forum.dlang.org/post/uzocokshugchescbawlj@forum.dlang.org
>
> Package-level documentation seems to be missing from the auto-generated documentation.

I think I generated the docs before there were any, let me go see.

> The gen_ut_main link on the side bar is also a 404.

Good catch, I'll take a look. I'm not looking forward to trying to recreate the site... it really should be easier.

>
> std.experimental.testing.options.Options and std.experimental.testing.reflection.TestData fields have no DDoc, so they don't show up in the generated documentation.

I'll add DDoc.


> Is there going to be a shouldEqual that's specialized for floating point, or should shouldBeTrue(approxEqual(...)) be used instead? (If so, this should be documented)

Good question.

> std.experimental.testing.testcase.TestCase.numTestsRun should be @property?

Sure.


Atila

On 09-Sep-2015 18:20, Robert burner Schadek wrote:
> This post marks the start of the two week review process of
> std.experimental.testing.
>
> PR: https://github.com/D-Programming-Language/phobos/pull/3207
> Dub: http://code.dlang.org/packages/unit-threaded
> Doc: See CyberShadow/DAutoTest for up-to-date documentation build
>
> Previous Thread:
> http://forum.dlang.org/post/uzocokshugchescbawlj@forum.dlang.org

Where is the announce thread?

-- 
Dmitry Olshansky

On Thursday, 10 September 2015 at 14:03:31 UTC, Dmitry Olshansky wrote:
> On 09-Sep-2015 18:20, Robert burner Schadek wrote:
>> This post marks the start of the two week review process of
>> std.experimental.testing.
>>
>> PR: https://github.com/D-Programming-Language/phobos/pull/3207
>> Dub: http://code.dlang.org/packages/unit-threaded
>> Doc: See CyberShadow/DAutoTest for up-to-date documentation build
>>
>> Previous Thread:
>> http://forum.dlang.org/post/uzocokshugchescbawlj@forum.dlang.org
>
> Where is the announce thread?

http://forum.dlang.org/post/tekjnfyvvmrozmqixtro@forum.dlang.org

On Wednesday, 9 September 2015 at 18:54:30 UTC, Brian Schott wrote:
> On Wednesday, 9 September 2015 at 15:20:41 UTC, Robert burner Schadek wrote:
>> This post marks the start of the two week review process of std.experimental.testing.
>>
>> PR: https://github.com/D-Programming-Language/phobos/pull/3207
>> Dub: http://code.dlang.org/packages/unit-threaded
>> Doc: See CyberShadow/DAutoTest for up-to-date documentation build
>>
>> Previous Thread: http://forum.dlang.org/post/uzocokshugchescbawlj@forum.dlang.org
>
> Package-level documentation seems to be missing from the auto-generated documentation.
>
> The gen_ut_main link on the side bar is also a 404.
>
> std.experimental.testing.options.Options and std.experimental.testing.reflection.TestData fields have no DDoc, so they don't show up in the generated documentation.


The autotester docs are... different from `make html`. I fixed it, but just in case here's my version of dlang.org with the docs:

http://atilaneves.github.io/phobos/

> Is there going to be a shouldEqual that's specialized for floating point, or should shouldBeTrue(approxEqual(...)) be used instead? (If so, this should be documented)

Implemented in the latest version and unit tested.


Atila

On Wednesday, 9 September 2015 at 15:20:41 UTC, Robert burner Schadek wrote:
> This post marks the start of the two week review process of std.experimental.testing.
> </ snip>

Some questions from a Java programmer:
How would I go about making test fixtures. Ex. in JUnit you have @Before and @BeforeClass
Is it possible to categorize tests?
How about Fuzz-tests, randomize input for test on each run?
Time limited test? If this tests runs more than 5min then fail

On Friday, 11 September 2015 at 10:02:22 UTC, NVolcz wrote:
> On Wednesday, 9 September 2015 at 15:20:41 UTC, Robert burner Schadek wrote:
>> This post marks the start of the two week review process of std.experimental.testing.
>> </ snip>
>
> Some questions from a Java programmer:
> How would I go about making test fixtures. Ex. in JUnit you have @Before and @BeforeClass

The py.test way: write a function that creates the fixture, call it from the unit test.

> Is it possible to categorize tests?

D's module system does that already.

> How about Fuzz-tests, randomize input for test on each run?

Like QuickCheck? Robert has something for that.

> Time limited test? If this tests runs more than 5min then fail

Unit tests should run in a fraction of a second... no, there's no such functionality.

Atila

On Friday, 11 September 2015 at 11:27:59 UTC, Atila Neves wrote:
> On Friday, 11 September 2015 at 10:02:22 UTC, NVolcz wrote:
>> Is it possible to categorize tests?
>
> D's module system does that already.

Along with things like version(unittestFeatureA) or version(unittestPrecision)

On 2015-09-11 13:27, Atila Neves wrote:

> Unit tests should run in a fraction of a second... no, there's no such
> functionality.

Why would I not use this for other kinds of tests?

-- 
/Jacob Carlborg