14/03/07 Change requirements with FIT/FitNesse2 Iterative Software development + system increment Prioritized functionalities Write acceptance tests Execute acceptance tests Write and execute unit tests At different points in the process Executed after the developmentWritten before
14/03/07 Change requirements with FIT/FitNesse3 Bibliographic system The Bibliographic system is a desktop application that helps a secretary to manage Bibliographic documents. A document has the following fields: author, title, year of publication and price. The secretary can search that information for values he/she specify.
14/03/07 Change requirements with FIT/FitNesse4 Search The search is case- sensitive and use partial matches. Suppose that the database is populated with the data: Suppose to have the GUI on the right. If you insert Ceccato and click Find the result is: F. Ricca, Paolo Tonella # Analysis of Web Applications # 2001 # Alessandro Marchetto, Filippo Ricca # Testing of Ajax Web applications # 2007 # M. Ceccato # AOP is OK? # 2004 # M. Ceccato, F. Ricca # OOP vs. AOP # 2005 # 5 Ceccato M. Ceccato # AOP is OK? # 2004 M. Ceccato, F. Ricca # OOP vs. AOP # 2005
14/03/07 Change requirements with FIT/FitNesse5 Acceptance Testing for a change requirement A change requirement is expressed as a fit table that does not pass the tests. inputs output
14/03/07 Change requirements with FIT/FitNesse6 Developers have to change the code in order to make the tests pass. Acceptance Testing for a change requirement
14/03/07 Change requirements with FIT/FitNesse7 Exercise Download the eclipse project here: _Change_Requirement.zip Import it in eclipse. Read and run the a change requirement. Fix the application code in order to make the tests pass. Record the time you use to apply change tasks.