Thread overview | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
April 04, 2017 Testing D codes | ||||
---|---|---|---|---|
| ||||
Attachments:
| 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: sip:russel.winder@ekiga.net 41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
|
April 04, 2017 Re: Testing D codes | ||||
---|---|---|---|---|
| ||||
Posted in reply to Russel Winder | Same as anywhere else. Integration test is a test that connects to a deployed system, which is different from unittest only in philosophical aspect. |
April 06, 2017 Re: Testing D codes | ||||
---|---|---|---|---|
| ||||
Posted in reply to Kagamin Attachments:
| On Tue, 2017-04-04 at 15:23 +0000, 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 deployed system would be a system test rather than an integration test – but then there are probably twice as many meanings to these terms as there are programmers. However the question remains are there any examples of good integration and system testing of D codes out there in the wild to use as exemplars. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net 41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder |
April 06, 2017 Re: Testing D codes | ||||
---|---|---|---|---|
| ||||
Posted in reply to Russel Winder | https://github.com/ikod/dlang-requests/blob/master/tests/app.d |
April 06, 2017 Re: Testing D codes | ||||
---|---|---|---|---|
| ||||
Posted in reply to Kagamin Attachments:
| On Thu, 2017-04-06 at 13:08 +0000, 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 there any need for the unittest block in the application created to run the integration tests? -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net 41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder |
April 06, 2017 Re: Testing D codes | ||||
---|---|---|---|---|
| ||||
Posted in reply to Russel Winder | 06.04.2017 16:49, Russel Winder via Digitalmars-d-learn пишет: > On Thu, 2017-04-06 at 13:08 +0000, 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 there any need for the unittest block in the application created to > run the integration tests? > 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. |
April 06, 2017 Re: Testing D codes | ||||
---|---|---|---|---|
| ||||
Posted in reply to drug Attachments:
| 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 primitive. Useful, but primitive. At some point though shrinking is going to have to be implemented for the property-based testing stuff in unit-threaded. The sandbox is looking most useful for integration tests. I am still wondering about separating integration and system tests out of the module source leaving the unit tests in the module source. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net 41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder |
April 07, 2017 Re: Testing D codes | ||||
---|---|---|---|---|
| ||||
Posted in reply to Russel Winder | 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 for more advanced testing only.
|
April 07, 2017 Re: Testing D codes | ||||
---|---|---|---|---|
| ||||
Posted in reply to Russel Winder | 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 best for the most basic stuff.
|
April 10, 2017 Re: Testing D codes | ||||
---|---|---|---|---|
| ||||
Posted in reply to drug Attachments:
| 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. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net 41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder |
Copyright © 1999-2021 by the D Language Foundation