• Russel Winder (13/13) Dec 21 2013 Is there a way of mocking the TCPConnect call so as to create a
• Dicebot (4/8) Dec 22 2013 By forking vibe.d repository. No out-of-the-box way to redefine

Russel Winder <russel winder.org.uk> writes:

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?

--=20
Russel.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder ekiga.n=
et
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

"Dicebot" <public dicebot.lv> writes:

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.