Development process of level 2 API for CI support at Nokia Networks
Gudenko, Oleksandr (2022)
2022
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-202204296566
https://urn.fi/URN:NBN:fi:amk-202204296566
Tiivistelmä
This thesis documents the experience and steps taken during the Level 2 API development at Nokia Networks. A Level 2 API is a higher-level API collection that has advanced computing features and, in some cases, can utilise a main Level 1 API to create-read-update-delete, a collection of CRUD requests to achieve the results. The goal of this thesis project is to describe the process and environment during the development of the Level 2 API.
The project follows a development of a new feature set for a configuration da-tabase project, named configDB, which is a web application written with Node JS and React JS. The configurations, which configDB manages, are stored in the JSON form, they are collected to create a test suite for radio software under testing. The finished test suite is exported to a Robot Framework script which is used during the CI test run.
The result of the study highlights the challenges with project development while contributing to the larger team effort. Unexpected interruptions, such as bug reports and parallel project support requests, resulted in partial thesis project implementation.
The project follows a development of a new feature set for a configuration da-tabase project, named configDB, which is a web application written with Node JS and React JS. The configurations, which configDB manages, are stored in the JSON form, they are collected to create a test suite for radio software under testing. The finished test suite is exported to a Robot Framework script which is used during the CI test run.
The result of the study highlights the challenges with project development while contributing to the larger team effort. Unexpected interruptions, such as bug reports and parallel project support requests, resulted in partial thesis project implementation.