Introducing test-driven development in web and mobile development teams: methods and effects
| dc.contributor.author | Vainiotalo, Petteri | |
| dc.contributor.department | fi=Tietotekniikan laitos|en=Department of Computing| | |
| dc.contributor.faculty | fi=Teknillinen tiedekunta|en=Faculty of Technology| | |
| dc.contributor.studysubject | fi=Tietotekniikka|en=Information and Communication Technology| | |
| dc.date.accessioned | 2023-06-20T21:02:48Z | |
| dc.date.available | 2023-06-20T21:02:48Z | |
| dc.date.issued | 2023-06-19 | |
| dc.description.abstract | Keeping up with constantly changing requirements has become a necessity in the field of software development. Web and mobile applications are especially relevant here, as they are widespread to large amounts of everyday users. Maintaining these applications require means of keeping them up to date while preventing regressions. Software testing in its various forms on different levels is the fundamental way to achieve this. Still, the need to continuously deliver new updates and features can cause testing to become neglected and detached from the development process. One way to address this is to introduce a test-first approach to the development process, namely test-driven development. It encourages writing tests before writing code, ensuring that tests exist while promoting testability. The research presented in this thesis focuses on the opinions and experiences of developers who are a part of a development team working on a web and mobile applicaton. A process of transitioning from a more traditional test-last approach to test-driven development was started for the team. The purpose of this was to find out what obstacles developers face when using a new method, what emotions they experience, what they think about test-driven development and its applicability in practice, and how well they adopt it. The results demonstrated what factors contribute to a successful transition to test-driven development, as well as the team-wide adoption of development methods in general. Applying suggestions made in previous studies to the setting in the team made the transition possible, and the introduction of the method had a mostly positive and unifying effect on existing testing practices. | |
| dc.format.extent | 89 | |
| dc.identifier.olddbid | 192430 | |
| dc.identifier.oldhandle | 10024/175508 | |
| dc.identifier.uri | https://www.utupub.fi/handle/11111/24445 | |
| dc.identifier.urn | URN:NBN:fi-fe2023062057216 | |
| dc.language.iso | eng | |
| dc.rights | fi=Julkaisu on tekijänoikeussäännösten alainen. Teosta voi lukea ja tulostaa henkilökohtaista käyttöä varten. Käyttö kaupallisiin tarkoituksiin on kielletty.|en=This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.| | |
| dc.rights.accessrights | suljettu | |
| dc.source.identifier | https://www.utupub.fi/handle/10024/175508 | |
| dc.subject | test-driven development, development methods, testing methods | |
| dc.title | Introducing test-driven development in web and mobile development teams: methods and effects | |
| dc.type.ontasot | fi=Diplomityö|en=Master's thesis| |
Tiedostot
1 - 1 / 1
Ladataan...
- Name:
- Vainiotalo_Petteri_opinnayte.pdf
- Size:
- 1.22 MB
- Format:
- Adobe Portable Document Format