Razvoj softvera vođen testiranjem

master's thesis

• Author: Hrvoje Bedeković
• Mentor: Robert Manger (mentor)
• Committee member: Robert Manger (predsjednik povjerenstva)
• Committee member: Vedran Čačić (član povjerenstva)
• Committee member: Goran Igaly (član povjerenstva)
• Committee member: Goranka Nogo (član povjerenstva)
• Granter: University of Zagreb; Faculty of Science; (Department of Mathematics); Zagreb
• Defense date and country: 2016-12-01, Croatia
• Scientific / art field, discipline and subdiscipline: NATURAL SCIENCES; Mathematics

Abstract

Razvoj softvera vođen testiranjem se krenuo koristiti radi želje programera da se u programu implementiraju samo potrebne metode i kako bi im testovi na vrijeme otkrili da li trenutna verzija programa radi ono što treba. Najčešće se ovaj način razvoja softvera koristi u manjim projektima, ali zbog sve veće popularnosti kreće se sve više koristiti u većim projektima.Razvoj softvera vođen testiranjem se sastoji od tri faze. Prva faza se sastoji od pisanja testova za metode koje još nisu implementirane. U drugoj fazi pišemo metode koje će proći napisane testove. U trećoj fazi se brinemo o kvaliteti koda, jednostavnosti održavanja i jednostavnosti čitanje koda. Kako se razvoj softvera vođen testiranjem krenuo sve više koristiti tako su se zamijetili određeni obrasci koji se najčešće pojavljuju. Obrasci se pojavljuju u sve tri faze razvoja softvera. Iako su neki očiti, preporučeno je poznavanje svih obrazaca prije početka korištenja ovog načina razvoja softvera. Njihovo poznavanje će umanjiti vrijeme potrebno za implementiranje metoda i smanjit će broj pogrešaka. Kod razvoja softvera vođenog testiranjem bitno je koristiti programski jezik koji ima aplikacijski okvir za testiranje dijelova. To nije presudan uvjet ali on olakšava razvoj softvera. Aplikacijski okviri sadrže mnogo korisnih metoda koje će poslužiti programeru.

Abstract (english)

Usage of test-driven development was started because programmers wanted to implement only the necessary methods in their programmes and so the tests could reveal if the current version of the program is working as expected. This method is commonly used in smaller projects, but because of the increasing popularity it is getting more and more used in bigger projects. Test-driven development has three phases. The first (red) phase consists of writing tests for methods that are not yet implemented. In the second (green) phase we write methods that will pass the written tests. In the third (refactor) phase we are concerned about code quality, code maintenance and code reading simplicity. As test-driven development was more and more used, programmers started to notice patterns. Patterns occur in all three phases in software development. Although some are simple it is recommended to learn all of the patterns before using this type of software development. Pattern recognition will decrease time needed for method implementation al will decrease the number of errors. In test-driven development it is important to use a programming language that has a unit test framework. This is not a crucial requirement but it simplifies software development. Frameworks have a lot of useful methods that will be at disposal to the programmer.

• Keywords: razvoj softvera; agilne metode; razvoj softvera vođen testiranjem; TTD
• Keywords (english): software development; agile methods; test-driven development; TTD
• Language: croatian
• URN:NBN: urn:nbn:hr:217:389505
• Study programme: Title: Computer Science and Mathematics; Study programme type: university; Study level: graduate; Academic / professional title: magistar/magistra računarstva i matematike (magistar/magistra računarstva i matematike)
• Type of resource: Text
• File origin: Born digital
• Access conditions: Open access
• Created on: 2017-01-30 12:35:54