1 / 7

Change requirements with FIT / FitNesse

Ceccato Mariano ITC-Irst Trento, Italy ceccato@itc.it. Change requirements with FIT / FitNesse. Iterative Software development. “At different points in the process”. Write and execute unit tests. Execute acceptance tests. Write acceptance tests. increment. +. system. Prioritized

kelsie-guthrie
Télécharger la présentation

Change requirements with FIT / FitNesse

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ceccato Mariano ITC-Irst Trento, Italy ceccato@itc.it Change requirements with FIT / FitNesse Change requirements with FIT/FitNesse

  2. Change requirements with FIT/FitNesse Iterative Software development “At different points in the process” Write and execute unit tests Execute acceptance tests Write acceptance tests increment + system Prioritized functionalities “Written before” “Executed after the development”

  3. Change requirements with FIT/FitNesse 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.

  4. F. Ricca, Paolo Tonella # Analysis of Web Applications # 2001 # 5 ------------------------------------------------------------ Alessandro Marchetto, Filippo Ricca # Testing of Ajax Web applications # 2007 # 8 ------------------------------------------------------------ M. Ceccato # AOP is OK? # 2004 # 7 ------------------------------------------------------------ M. Ceccato, F. Ricca # OOP vs. AOP # 2005 # 5 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: Ceccato M. Ceccato # AOP is OK? # 2004 M. Ceccato, F. Ricca # OOP vs. AOP # 2005 Change requirements with FIT/FitNesse

  5. Acceptance Testing for a change requirement • A change requirement is expressed as a fit table that does not pass the tests. inputs Change requirements with FIT/FitNesse output

  6. Change requirements with FIT/FitNesse Acceptance Testing for a change requirement • Developers have to change the code in order to make the tests pass.

  7. Change requirements with FIT/FitNesse Exercise • Download the eclipse project here: http://sra.itc.it/people/ceccato/courses/lsa/files/bibliographic_System_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.

More Related