Test driven development uzori i refaktorisanje testnog koda

Abstract

Test driven development (TDD) je proces razvoja softvera nastao kao deo Ekstremnog programiranja, da bi ga kasnije usvojile sve agilne metodologije. Glavna tačka u agilnim metodologijama je softver koji radi, a TDD je proces koji je fokusiran na proizvodnju pouzdanog softvera koji se lako održava. TDD menja ulogu koju testiranje ima u procesu razvoja softvera i ne služi više samo da otkrije greške u sistemu, već pomaže projektnom timu da bolјe razume funkcionalnosti potrebne korisniku. TDD proces se zasniva na ponavlјanju kratkog razvojnog ciklusa u kome se korisnički zahtevi pretvaraju u testove, zatim se piše minimalna količina koda potrebna da ti testovi prođu i na kraju se kôd rafaktoriše. U ovom radu se govori o uzorima koji se primenjuju u TDD-u kao načinima za struktuiranje kôda tako da on bude prilagođeniji za testiranje. Takođe se navode uzori koji se koriste za pisanje jediničnih testova i uzori zelene faze koji nam pomažu da rešavanjem testova dođemo do odgovarajuće implementacije zahteva. Zatim se daje pregled test double objekata koji se koriste u testovima kao zamena za objekte koji će se koristiti u produkcionoj verziji.

Test driven development (TDD) is a software development process created as part of Extreme Programming, but has since been adopted by all of the other Agile methods. A central point in agile methods is working software and TDD is a process that is focused on producing reliable and maintainable software. TDD changes the role that testing has in the software development process and is no longer used only to detect errors in the system, but also helps the project team to better understand the functionality needed by the user. TDD process is based on the repetition of a short development cycle in which user requirements are transformed into tests, then write the minimum amount of code to pass that test, and at the end code is refactored. This paper discusses the patterns that are used in TDD as a way of structuring the code so that it is adapted for testing. Also referred to patterns that are used for writing unit tests and the green phase patterns that help us to, by making tests pass, get appropriate implementation of the requirements. It then provides an overview of the test double objects used in the tests as a substitute for the objects that will be used in production.