Skip to main content

build-setup

Set up build environment and test fixtures for COBOL-to-Java migrations. Creates compilation infrastructure for both languages and generates golden test data.

来源信息

仓库
OpenHands/extensions
最近来源活动
2026年7月1日 22:49
检测到的 SKILL.md 语言
英语
星标
175
Forks
119

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

文件资源管理器
2 个文件

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
build-setup
description
Set up build environment and test fixtures for COBOL-to-Java migrations. Creates compilation infrastructure for both languages and generates golden test data.
license
MIT
compatibility
Requires GnuCOBOL (cobc), Java 11+, Maven or Gradle
triggers
["cobol build","cobol test fixtures","migration build setup","gnucobol"]
Set up a build environment and create test fixtures for validating COBOL-to-Java migrations. To install GnuCOBOL, run: `./scripts/install-gnucobol.sh` On Windows, run that shell script from Git Bash/WSL (`bash scripts/install-gnucobol.sh`) or install GnuCOBOL with a Windows package manager and document the chosen command in `build_notes.md`. ## Phase 1: Build Setup ### COBOL Build - Find a way to compile and run the COBOL code (e.g., GnuCOBOL) - Verify at least one program compiles and executes - Note any dependencies or setup required ### Java Build - Initialize a Java project alongside the COBOL code (Maven or Gradle) - Set up standard directory structure: `src/main/java`, `src/test/java` - Include JUnit 5 as a test dependency - Verify the project builds (even if empty) ## Phase 2: Test Fixture Generation For each major COBOL program: ### Create Synthetic Test Inputs - Save to: `test-fixtures/inputs/{PROGRAM_NAME}/` - Create 3-5 test cases per program covering: - Normal/happy path (valid, typical data) - Edge cases (empty input, maximum values, boundary conditions) - Error cases (invalid formats, missing required fields) ### Generate Golden Outputs - Run each COBOL program with each test input - Save COBOL output to: `test-fixtures/expected_outputs/{PROGRAM_NAME}/` - These become the "golden" outputs that Java must match ### Create Test Manifest Save to `test_manifest.json`: ```json { "PROGRAM1": { "description": "Brief description of what this program does", "test_cases": [ { "name": "normal_invoice", "input": "inputs/PROGRAM1/test_001.dat", "expected": "expected_outputs/PROGRAM1/test_001.out", "description": "Happy path" } ] } } ``` ## Deliverables 1. **build_notes.md** — Build instructions for COBOL and Java 2. **test-fixtures/** — Directory with `inputs/` and `expected_outputs/` 3. **test_manifest.json** — JSON manifest of all test cases ## Priority Focus on programs with core business logic (transactions, calculations, data processing). UI-heavy programs (menu screens, reports) are lower priority.
在 GitHub 查看