开云体育

Hi Esko, i read the same book recently, and also found that it was hard to apply all these new ideas on a project : At each step there were so many questions, i had to keep on re-reading parts of the

Great thanks guys for all the resources/ideas.

xxtommo54xx wrote on 18.7.2012 0:25: The people on this mailing list don't appear to do much end-to-end testing. It might be best that you ask your question on

+1

+1 Put another way: perhaps your real system is not as free as you think it is. Anything that takes extra time or introduces uncertainty is not "free" in the sense that it takes additional resources

On Tue, Jul 17, 2012 at 10:16 PM, xxtommo54xx <xxtommoxx@...> wrote: > Basically i am supposed to send a message to keep a connection that has a timeout value alive. The message is dependent on

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

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

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

Hi, Are you writing an app which acts as an http client? If not, it's not clear to my why you would want to test sending an http request. Assume that any code you're not writing yourself works, and

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,

The premise was quite interesting - see the answers to interesting and important questions stacked up next to each other, and see the differences in how people approach each problem. Then I read the

In the last couple of months several online discussions took place about test first vs test last, code-to-test ratios or whether BDD is really just TDD. InfoQ asked renown TDD and BDD experts to give

Thank you Kay... It was a chaotic road... and a fresh set of eyes is helpful... I'll get an updated posted this evening. _Marvin

... hmmm ... anytime we design a method aren't we "storyboarding a GUI"??? Said another way, as we move from worrying exclusively about whether the execution is "correct" to greater code

Interesting. From the article: Really? I suppose it depends on what "just sketching something out" means. If he means, "do an informal object diagram" or "write a summary of the intended behavior" and

I read this a week or so ago. This is similar to the Lean Startup advice. The premise being you do not know what is required. So you make an assumption, quickly code it up, put it out there

Thank you!! Kay

[ snip ] I spotted four try-finally blocks, three of which appear to be identical except for the number of tasks. I'd probably first refactor the number of tasks into a variable, extract the block

Hey, Edmund, How are you? Thanks for calling out the single Assert and the fact that it can never fail. I think the first post I ever made to the XP list was something like "how do you tell when your