How was the development process organized in your team (CI/CD, testing, code review)?

In our team, the development process was organized as follows:

• CI/CD: We used GitLab CI for automated build and deployment. Each commit triggered a pipeline with stages for build, testing, and staging deployment. After successful testing on staging, a manual release to production was performed.

• Testing: We wrote unit tests covering key modules, integration tests to verify service interactions, and end-to-end tests for critical user scenarios.

• Code Review: All changes underwent mandatory code review via merge requests. Usually, 1-2 colleagues checked the code for readability, architecture, and compliance with standards. Discussions took place directly in the MR, which helped improve quality and share knowledge.

Example of a GitLab CI configuration for a Go project:

stages:
  - build
  - test
  - deploy

build:
  stage: build
  script:
    - go build -v ./...

test:
  stage: test
  script:
    - go test -v ./...

deploy_staging:
  stage: deploy
  script:
    - ./deploy.sh staging
  when: manual
  only:
    - develop

deploy_production:
  stage: deploy
  script:
    - ./deploy.sh production
  when: manual
  only:
    - master

This process ensured stability and quick feedback.