Read through the stories again, and choose some to implement
that sounds good - but what language will we use? Of course I'd recommend Python... BurkhardKlossPython people dropped like...flies (didn't scale (ugh))
Let's use a mixture, I'd like to learn [J]Python, I'll pair with a python programmer. -- OliBye
OliBye suggests other stories are done in Java, and Kev (who hates Java) should pair and learn Java.
<gulp>KevinHutchinson also feels the time may be right to expose himself to Java</gulp>
Allow 15 mins for introductions before, and 30 mins after for observations about the activity(suggested by PaulSimmons).
Decided on a 45 minute iteration plan of one story Put some words in a page..., no idea what the load factor would be, since this is the first interation.
Here's what we did xpdeveloper.com/cgi-bin/cvsweb.cgi/xtc/ It took 2.5 hours to implement things, i'm not sure DoingTheLoadFactor? on this granularity of time holds water.
We then wrote the PageSaver? class to get this test running. Notice that this code only uses an instance variable to "save". However this is enough to get the test running.
We versioned this work in [Xtc.xtc0_99] as our first running example.
Displaying a string in a web page
First we tried to write "TestEdit?.testDisplaying" that calls doGet on a servlet. We envisioned extending our PageSaver? to be a servlet and calling PageSaver?.doGet to display the text we can already save. Leaving changing the text via HTTP until the next EngineeringTask?.
When we wrote the servlet code, we discovered that our test failed. A closer examination of doGet revealed that we needed to mock up request and response objects. These objects have big interfaces that are a lot of work to create. We decided to try an alternative approach (our task was in danger of taking too long, we had already spent 20 minutes). We had a bit of experience writing HTTP request code, so we clipped it from an example to help us move on with our test. This didn't feel so great, but we wanted to get something running
we added and refactored the test testDisplayingAKnownString to test saving some known input and getting the servlet to reply that known input via Http.