December 21, 2013 Vibe.d and testing | ||||
---|---|---|---|---|
| ||||
Attachments:
| Is there a way of mocking the TCPConnect call so as to create a connection to a mock instead of the real device so as to be able to integration test and system test a vibe.d-based client?
--
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
|
December 22, 2013 Re: Vibe.d and testing | ||||
---|---|---|---|---|
| ||||
Posted in reply to Russel Winder | On Saturday, 21 December 2013 at 15:08:48 UTC, Russel Winder wrote:
> Is there a way of mocking the TCPConnect call so as to create a
> connection to a mock instead of the real device so as to be able to
> integration test and system test a vibe.d-based client?
By forking vibe.d repository. No out-of-the-box way to redefine default TCP handling routines from user code if you mean that.
|
Copyright © 1999-2021 by the D Language Foundation