The role of testing in Agile software development
Kemppainen, Paavo (2020)
Kemppainen, Paavo
2020
Tieto- ja sähkötekniikan kandidaattiohjelma - Bachelor's Programme in Computing and Electrical Engineering
Informaatioteknologian ja viestinnän tiedekunta - Faculty of Information Technology and Communication Sciences
This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Hyväksymispäivämäärä
2020-09-15
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:tuni-202010147347
https://urn.fi/URN:NBN:fi:tuni-202010147347
Tiivistelmä
Software testing is one of the most important phases in software projects because it is used to verify the work that is done and the quality of the work for both the programmer and the client. Testing processes and methods have been advancing side by side software development for years. One of the most common software development types is Agile where the Agile testing also gets its name.
This thesis studies the use of different methods for testing software which together form Agile testing processes. Conclusions in this thesis are based on a couple of well-known pieces on the subject with the help of online material from different opinions. With these source materials, the thesis aims to clarify how different testing methods and processes differ from each other. After this, the thesis represents a consensus on what good and what bad these methods and processes bring to a software project.
The thesis concludes that finding the right testing methods and processes is not easy and one usually has to have some experience selecting them. Every project has its own needs and that way the methods and processes differ between them. One of the most important finds is that the customer is usually in close contact with the testing as they are the ones that define the requirements. A couple of ways to implement this are said in this thesis.
This thesis studies the use of different methods for testing software which together form Agile testing processes. Conclusions in this thesis are based on a couple of well-known pieces on the subject with the help of online material from different opinions. With these source materials, the thesis aims to clarify how different testing methods and processes differ from each other. After this, the thesis represents a consensus on what good and what bad these methods and processes bring to a software project.
The thesis concludes that finding the right testing methods and processes is not easy and one usually has to have some experience selecting them. Every project has its own needs and that way the methods and processes differ between them. One of the most important finds is that the customer is usually in close contact with the testing as they are the ones that define the requirements. A couple of ways to implement this are said in this thesis.
Kokoelmat
- Kandidaatintutkielmat [8997]