Feature 023


Feature ID	FEA023
Subsystem the feature is part of	Epic 08: Bug Fixes
Responsible person	Helminen Valtteri
Status	proposal

Description

Integrate with version control systems (e.g., Git)


US030
US032
US101

Preliminary user stories

US030: As an Operations engineer, I want to fetch the latest, stable production code from the version control system so I can deploy or rollback in case of any changes.

This user story focuses on enabling operations engineers to fetch the latest stable production code from the version control system. The key outcome of this feature is to ensure that operations engineers can quickly retrieve and deploy the most up-to-date and stable version of the code. This also provides the ability to easily roll back to a previous version if necessary, minimizing downtime and mitigating any potential issues that arise after deploying new changes. By having access to stable production versions, operations engineers can ensure smoother deployments and effective recovery from any unforeseen issues.

US032: As a Team Leader, I want to track commits made by my team members to ensure proper version control usage.

This user story focuses on implementing a system that allows team leaders to track commits made by team members to ensure proper version control usage. The key outcome of this feature is to enable team leaders to efficiently monitor commit practices, ensure consistency in code contributions, and identify any issues related to version control usage. By having access to detailed commit histories, including commit messages and timestamps, team leaders can proactively guide the team toward following best practices, ensuring the repository remains organized and well-maintained.

US101: As a Developer, I would like to use Git Branching for Bug Fixing.

This user story focuses on implementing Git branching strategies specifically for bug fixing. The key outcome of this feature is to allow developers to create isolated branches for each bug fix, enabling them to work on issues without affecting the main or production codebase. By utilizing Git branches for bug fixing, developers can work independently, ensure that fixes are thoroughly tested before being merged, and maintain a clean and organized version control system.

Test case ideas and acceptance criteria

US030

Example test case	Acceptance criteria
Test if previous version are available after an update	Previous version are available and can be rolled back to
Test if code rolls back correctly without overlapping (having both codes at the same time)	Roll back without code overlapping

US032

Example test case	Acceptance criteria
Test if git commit are shown	commit histories are visible

US101

Example test case	Acceptance criteria
Test if branching happens correctly	Developer are able to work on the code in their own branch without affecting other code
Test if branch merging goes smoothly	Merge is acheivable without breaking the codebase