When designing a software, it was commonplace to use specialised techniques to ensure quality of the final product. Continuous Integration (CI) provides developers a strategy by allowing for teams to continuously add to their project daily without conflicting with prior work. An automated process would check that these new integration additions are functional so that any faults were quickly identified for correction. Continuous Integration played a pivotal role in organisations that developed software solutions for their own or their customers’ processes. It comes as no shock that an abundance of research illustrates its importance and success in software development. Automated testing was praised so much so that there was a distinct lack of negatives particularly in the professional industry. The goal of this study was to gather knowledge about automated testing in a work environment so that principles for implementing automated testing. This was conducted by a qualitative case study while looking at the developer/user perspective. This was done by conducting semi-structured interviews with employees working with automated testing in a telecommunication organisation. The study’s results presented eight themes that the informants and prior literature studies observed as issues of importance. These themes showed that the automated testing had experienced problems in practice that were not noticed in academical papers and for that, seven recommendations were presented for other organisations to be observant of.
| Identifer | oai:union.ndltd.org:UPSALLA1/oai:DiVA.org:uu-478095 |
| Date | January 2022 |
| Creators | Moezzi, Aryan Adrian, Siskina, Irina |
| Publisher | Uppsala universitet, Informationssystem |
| Source Sets | DiVA Archive at Upsalla University |
| Language | English |
| Detected Language | English |
| Type | Student thesis, info:eu-repo/semantics/bachelorThesis, text |
| Format | application/pdf |
| Rights | info:eu-repo/semantics/openAccess |
Page generated in 0.0024 seconds