10.04.2017 19:20, Russel Winder via Digitalmars-d-learn пишет:
On Fri, 2017-04-07 at 11:40 +0300, drug via Digitalmars-d-learn wrote:
[…]
I do this. I have unittests in the module sources and have a
separate
subpackage intended for more advanced testing only.
Do you have an example project
On Fri, 2017-04-07 at 11:40 +0300, drug via Digitalmars-d-learn wrote:
>
[…]
> I do this. I have unittests in the module sources and have a
> separate
> subpackage intended for more advanced testing only.
Do you have an example project I could take a look at?
--
Russel.
On Thursday, 6 April 2017 at 13:49:11 UTC, Russel Winder wrote:
Is there any need for the unittest block in the application
created to run the integration tests?
If you don't care to call each and all of them by hand. Test
frameworks are handy for extensive testing, builtin unittests
work
06.04.2017 19:34, Russel Winder via Digitalmars-d-learn пишет:
I am still wondering about separating integration and system tests out
of the module source leaving the unit tests in the module source.
I do this. I have unittests in the module sources and have a separate
subpackage intended
On Thu, 2017-04-06 at 16:57 +0300, drug via Digitalmars-d-learn wrote:
>
[…]
> I'm not sure about terminology too, but did you try some like
> https://code.dlang.org/packages/unit-threaded?
> I use it and am satisfied.
I was slowly sidling up to using this as the inbuilt system is a tad
06.04.2017 16:49, Russel Winder via Digitalmars-d-learn пишет:
On Thu, 2017-04-06 at 13:08 +, Kagamin via Digitalmars-d-learn
wrote:
https://github.com/ikod/dlang-requests/blob/master/tests/app.d
Which implies that in the D milieu all tests are unittests even if they
are not unittests.
On Thu, 2017-04-06 at 13:08 +, Kagamin via Digitalmars-d-learn
wrote:
> https://github.com/ikod/dlang-requests/blob/master/tests/app.d
Which implies that in the D milieu all tests are unittests even if they
are not unittests. Sad use of terminology and jargon, but I can see it
working.
Is
https://github.com/ikod/dlang-requests/blob/master/tests/app.d
On Tue, 2017-04-04 at 15:23 +, Kagamin via Digitalmars-d-learn
wrote:
> Same as anywhere else. Integration test is a test that connects
> to a deployed system, which is different from unittest only in
> philosophical aspect.
Well according to the standard definitions connecting to a
Same as anywhere else. Integration test is a test that connects
to a deployed system, which is different from unittest only in
philosophical aspect.
Are there any resources dealing with how to do integration and system
testing of D codes? Google invariably just leads me to unit testing.
--
Russel.
=
Dr Russel Winder t: +44 20 7585 2200 voip:
11 matches
Mail list logo
