Diary of Stability Engineer
Hannus, Jami (2023)
2023
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-202305098787
https://urn.fi/URN:NBN:fi:amk-202305098787
Tiivistelmä
In this thesis, the perspective of a Stability Engineer was followed for ten weeks at Profilence Oy, a Technical Quality Analysis Information Technology company located in Oulu, Finland. The thesis aimed to record the daily and weekly general tasks done and explain how stability testing is related to software testing.
The thesis consists of the theoretical part, the diary, and the conclusion. The theoretical part includes an introduction to the company, what software testing is, and how stability testing is related to software testing. The last part explains the tools and methods used and the workflow basics. The entries to the diary part were made daily and weekly with the inclusion of a weekly analysis of each working week.
The result showed that there are many different tasks, and every week there were some different tasks while some tasks repeated themselves on a weekly basis. Includes describing experiences how problems were solved and different issues that can arise during the process.
The thesis gives short descriptions of the typical day working in stability engineering. It is possible to advance into a role that requires less coding and more data analysis and prioritization of the most critical problems. A larger or in-depth study would give more insight into the process, but a large part of the first-hand experiences was truncated and censored for customer confidentiality.
The thesis consists of the theoretical part, the diary, and the conclusion. The theoretical part includes an introduction to the company, what software testing is, and how stability testing is related to software testing. The last part explains the tools and methods used and the workflow basics. The entries to the diary part were made daily and weekly with the inclusion of a weekly analysis of each working week.
The result showed that there are many different tasks, and every week there were some different tasks while some tasks repeated themselves on a weekly basis. Includes describing experiences how problems were solved and different issues that can arise during the process.
The thesis gives short descriptions of the typical day working in stability engineering. It is possible to advance into a role that requires less coding and more data analysis and prioritization of the most critical problems. A larger or in-depth study would give more insight into the process, but a large part of the first-hand experiences was truncated and censored for customer confidentiality.