Documenting and implementing DevOps good practices with test automation and continuous deployment tools through software refinement

Modelo de procesos representado en BPMN para guiar la implememtacion de prácticas de desarrollo de software en empresas muy pequeñas armonizando DEVOPS y SCRUM

“…Likewise, in [15], it is indicated that the starting point of an effective preventive quality process starts with versioning and triggers an automatic process of continuous integration, which inspects if the evolution of the code syntactically has not undergone negative changes (syntax errors) that prevent generating the deployable unit and allow continuous deployment to execute successfully. Additionally, the code should be standardized so that all team members develop the project the same way, thus making it easier to maintain its evolution and support.…”

“…Additionally, in [15], it is indicated that the same tool is capable of reviewing unit test coverage, which suggests that this practice ought to be adopted by teams if they want to increase the benefits obtained. Unit tests are conducted to check the quality of the developed code, guaranteeing its correctness (that the functionality does what it should), in addition to checking the cases where incorrect data is entered and how it handles exceptions that control failures and prevent the software from crashing due to mishandling.…”

“…The more detailed the test is in its correctness and error handling, the greater its coverage will be. Also, in [15], it is indicated that if the source code has been versioned and the quality controls of the CI and the SCA have been approved, the automated process performs the CD, and previously recorded functional test scripts can be executed automatically. This ensures that thorough automatic reviews of everything developed so far (functional and regression tests) can be done using tools.…”

“…Authors such as [15] and [18] agree that the first steps in practices recommended by DevOps for development teams point to versioning, integration, and continuous deployment, where versioning is the starting point of the process. To ensure the collective ownership of the code and its standardization, all members of the SDT work connected to a source code repository (versioner) where they centralize their changes, generating traceability and the possibility of immediate failure recovery.…”

“…Since the integration branch is the synchronization point of the code, the quality controls of the other practices should be triggered from here when the PR request is approved. Additionally, in [15], they suggest that it is advisable to include the execution of the unit tests (UT) within the CI before building the deployable unit. This is done to ensure that the developers have tested every code unit.…”