Implementing Code Quality Assurance in Monorepos: Git Submodules for Unit Testing and Code Owner Mechanisms

Background: Monorepo architectures manage multiple projects within a single repository, which simplifies code sharing but increases regression risks when modifying shared components. To mitigate these risks, automated testing and manual code reviews are established to intercept issues during the development phase.

Unit Testing via Git Submodules: Separating test code from production code using Git submodules isolates environments and reduces change management overhead. The implementation involves initializing a dedicated test repository, linking it to the main project, and configuring the testing environment. Depending on the submodule location, developers use symbolic links to connect Jest configurations and test cases. CI pipelines are automated to execute tests and track coverage, dynamically switching to matching feature branches to ensure test alignment.

git submodule add xxx.git(test_repo_git_url) test(local_directory)

// src/infrastructure/package.json { "scripts": { "test:init": "git submodule update --init && git submodule foreach git checkout origin/master && ln submodule/jest.config.js jest.config.js && eden-test", "test": "ln submodule/jest.config.js jest.config.js && eden-test" } }

#!/bin/bash # Recursive symlink creation script source_dir=${1:-../../test/infrastructure/src/utils} target_dir=${2:-test/utils} config_dir='../../test/infrastructure/jest.config.js' if [ ! -f 'jest.config.js' ]; then ln -s $config_dir jest.config.js fi for file in $source_dir/* do filename=$(basename $file) if [ -d $file ]; then mkdir -p "$target_dir/$filename" bash $0 "$file" "$target_dir/$filename" fi if [ -f $file ]; then ln -s "$PWD/$file" "$PWD/$target_dir/$filename" fi done echo "Symlinks created!"

# Initialize submodule - git submodule update --init # Enter submodule directory and switch branch - cd test/infrastructure # Prioritize matching branch, fallback to master - git checkout master - git show-branch $CI_EVENT_CHANGE_SOURCE_BRANCH &>/dev/null && git checkout $CI_EVENT_CHANGE_SOURCE_BRANCH || echo $CI_EVENT_CHANGE_SOURCE_BRANCH not exist # Return to project and run tests - cd ../../src/infrastructure - mkdir -p test - cp -r ../../test/infrastructure/src/utils test - npm i - npm run test

Manual Review and Code Owner Mechanism: To enforce accountability for shared code modifications, a CODEOWNERS file maps specific file paths to designated reviewers, requiring their approval before merging. The syntax supports standard glob patterns and directory-specific overrides. Furthermore, code review notifications are consolidated into dedicated messaging topics, reducing alert fatigue and centralizing discussions for improved collaboration efficiency.

# Each line is a rule, matched top to bottom # Example: /sample_feature/ @user1 @user2 *.js @user3 /sample_feature/*.js @group1

Conclusion: Combining automated unit testing with structured code reviews effectively safeguards code quality in monorepo environments. Future iterations may integrate AI capabilities to auto-generate test cases and assist in code analysis, further streamlining development workflows and reducing maintenance overhead.