Hi Everyone,
   I was asked how to write a test when nothing got coded.  Tests have to occur mentally before being tried out.  Each team has a specification (1-2 pages) from the client.  Most of you thought out a list of questions to ask.  Hard to test a question.  
   Agile methods tell us to make a rough list of what's required and focus on the item that is for sure needed and understandable.  State it as a requirement per Ch5 (3 parts, 1 3x5 card).  
   Then expand it to have subparts including build and integrate so you envision everyone doing some of it.  Then pick your part(s).  Think how to test.  Think about when the selected part is DONEDONE.  What test do you see running successfully?
   So don't let having questions keep you from stating requirements (simply), coordinating who starts where, and building something the client will say "great" about!  You know enough from the spec sheet(s).
       Best regards,
          Dr. DeBlois