On Tuesday, 29 September 2015 at 19:15:13 UTC, Meta wrote:
On Tuesday, 29 September 2015 at 14:34:42 UTC, Atila Neves
wrote:
runTests with no optional arguments will run the tests in
threads.
There's nothing about purity enforcement there. In fact, I
tried
using pure unit tests yesterday with
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.
Will `runTests` automatically assert that all pure unittests by
default are parallellized and all non-pure are serialized? If so
On Tuesday, 29 September 2015 at 10:45:23 UTC, Per Nordlöw 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.
Will `runTests` automatically assert that all pure unittests by
On Tuesday, 29 September 2015 at 14:34:42 UTC, Atila Neves wrote:
runTests with no optional arguments will run the tests in
threads.
There's nothing about purity enforcement there. In fact, I tried
using pure unit tests yesterday with std.experimental.testing
and couldn't. The compiler inferred
On Monday, 28 September 2015 at 10:03:14 UTC, Robert burner
Schadek wrote:
Review of std.experimental.testing formal review
the two weeks of the formal review phase are over.
The review thread was very shallow. Dicebot again expressed
this disaffection with the assert function names
"s
Review of std.experimental.testing formal review
the two weeks of the formal review phase are over.
The review thread was very shallow. Dicebot again expressed this
disaffection with the assert function names
"should(BeTrue|BeFalse|...)" No agreement could be found.
Personally, I'
On Sunday, 13 September 2015 at 09:59:18 UTC, Dicebot wrote:
1) being able to mark test case as fatal (i.e. if internal
handshake or sanity check fails there is no point in trying to
run other tests)
I'm leaning towards not including this now and concentrating on
getting it
approved - a PR
Sure, it isn't really important and does not impact my opinion
anyway. Was simply sharing experience of writing similar purpose
library.
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
On Sunday, 13 September 2015 at 09:59:18 UTC, Dicebot wrote:
On Saturday, 12 September 2015 at 14:50:32 UTC, Jacob Carlborg
wrote:
On 2015-09-12 15:34, Dicebot wrote:
I also don't like mixing unittest and higher level functional
tests
(with setup and cleanup phases) into the same buckets -
On Sunday, 13 September 2015 at 10:44:30 UTC, Atila Neves wrote:
2) being able to do weak ordering of tests (by defining strict
sequence of groups so that parallelization/randomization only
happens within such group) - I have used something as simple
as numerical priority value so far for my
On Tuesday, 15 September 2015 at 08:27:29 UTC, Dicebot wrote:
On Sunday, 13 September 2015 at 10:44:30 UTC, Atila Neves wrote:
2) being able to do weak ordering of tests (by defining
strict sequence of groups so that
parallelization/randomization only happens within such group)
- I have used
On Saturday, 12 September 2015 at 14:50:32 UTC, Jacob Carlborg
wrote:
On 2015-09-12 15:34, Dicebot wrote:
I also don't like mixing unittest and higher level functional
tests
(with setup and cleanup phases) into the same buckets - this
doesn't fit
nice with D module system. Latter should be
On Sunday, 13 September 2015 at 09:59:18 UTC, Dicebot wrote:
On Saturday, 12 September 2015 at 14:50:32 UTC, Jacob Carlborg
wrote:
On 2015-09-12 15:34, Dicebot wrote:
I also don't like mixing unittest and higher level functional
tests
(with setup and cleanup phases) into the same buckets -
On 09/11/2015 01:27 PM, Atila Neves wrote:
>> How about Fuzz-tests, randomize input for test on each run?
>
> Like QuickCheck? Robert has something for that.
There is also https://github.com/MartinNowak/qcheck for that.
On 2015-09-13 12:44, Atila Neves wrote:
I've never heard of functionality like that, but should be easy to
implement.
We're using that at work, but on a different level. We have two separate
jobs in Jenkins, one depends on the other one. If the first one fails,
the second one is not run.
On Friday, 11 September 2015 at 15:54:57 UTC, Jacob Carlborg
wrote:
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?
I guess you're right. In any case, getting
On 2015-09-12 11:52, Atila Neves wrote:
I guess you're right. In any case, getting what's in there to get
accepted is work enough as it is.
Yes, absolutely. I wasn't arguing for the feature, just the reason not
to add it :)
--
/Jacob Carlborg
On 2015-09-12 15:34, Dicebot wrote:
I also don't like mixing unittest and higher level functional tests
(with setup and cleanup phases) into the same buckets - this doesn't fit
nice with D module system. Latter should be placed in a separate
modules/package to avoid being picked up by rdmd & Co
On Saturday, 12 September 2015 at 14:50:32 UTC, Jacob Carlborg
wrote:
Not sure I understand the problem. Does this prevent one from
writing functional tests in a completely separate directory?
Nope but the fact that they are treated the same (no separate
category, no output separation, no
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
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
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.
Some questions from a Java programmer:
How would I go about making test fixtures. Ex. in JUnit you have
@Before and @BeforeClass
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.
Some questions from a Java programmer:
How would I go about making
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
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
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
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://forum.dlang.org/post/stbdckpfsysjtppld...@forum.dlang.org
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:
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
32 matches
Mail list logo
