¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Testdrivendevelopment
  2. Messages
Single Messages Topics Expanded Polls

Re: End To End Test

xxtommo54xx
 

Basically i am supposed to send a message to keep a connection that has a timeout value alive. The message is dependent on the protocol being used i.e http, rmi, etc. It is also supposed to manage a set of these and send the messages depending on some sort of event (ex. a timed trigger).

In the book they clearly outlined the core components for the skeletal design which is the sniper communicating to a fake xmpp auction which outputs the result to the ui.

I just have trouble identifying the core components for the skeleton which is used to kickstart the tdd proccess and how to test it. Would i be able to use an actual implementation as opposed to a fake implementation (like the fake auction server)? The book mentioned that one of the reasons they used a fake auction server was because querying the real auction server was not free. In my case, i can test using a real resource for free. Any suggestions?

Thanks!

--- In testdrivendevelopment@..., "jmilkiewicz@..." <jmilkiewicz@...> wrote:

Hi

If i understand your use case correctly i would start with fake Http
server. This way you could easily record its behavior - even if you decide
to switch to "real http server"one day it would be quite useful to have
some fake http server with behavior you can easily define in your tests.
Basically i am thinking of some corner cases like server not avialable,
server responds too slow and so on.

br Jakub

2012/7/17 xxtommo54xx <xxtommoxx@...>

**


Hi,

I'm new to tdd and i've read the book growing oo software. I'm trying to
incorporate tdd into a sample project. Basically the project is an api that
allows you to keep-alive various services, basically its a heartbeat. The
book says to start out by designing a skeleton that is enough to get your
application functioning and that which covers the core components. So the
simplest end-to-end test I can think of is to send an http request and make
sure the server received it. How should i structure this test? Should I
have a fake http server and make a request to it and assert that the server
received the request or should I just make a request to any arbitrary
working url and get its return code?

I feel that my test case does not really cover the core components since
the api has the ability to send keep alive requests to various services
based on some various kinds trigger. Any suggestions on how to start?

Thanks.



[Non-text portions of this message have been removed]
Join [email protected] to automatically receive all group messages.