Unify all testing Airs
- 主要言語
- Rust
- スター
- 96
- フォーク
- 39
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
We currently have several places where we store example or testing `.air` files for different use cases.
- [`codegen/ace/src/tests/airs`](https://github.com/0xMiden/air-script/tree/next/codegen/ace/src/tests/airs)
- [`air-script/tests`](https://github.com/0xMiden/air-script/tree/next/air-script/tests)
- [`parser/src/parser/tests/input`](https://github.com/0xMiden/air-script/tree/next/parser/src/parser/tests/input)
- [`docs/examples`](https://github.com/huitseeker/air-script/tree/452140e4e88a5698d23c4945df747e5ac18fae98/docs/examples)
Except perhaps for the examples in `docs/examples`, it seems like we could put all other testing source files in `air-script/tests`. While taking into account likely duplicates, it we could increase the number of test cases for the 3 components that rely on these (winterfell codegen, ace codegen, and parser).
コントリビューションガイド
調査の方向性
The issue lists four directories containing .air files. Start by examining each directory to understand the file structure and identify duplicates. The goal is to consolidate files from codegen/ace/src/tests/airs, parser/src/parser/tests/input, and possibly docs/examples into air-script/tests. Check for any existing test suites that depend on these file paths to ensure the consolidation doesn't break tests. A good first step is to run the existing tests for the parser and codegen components to verify they pass before moving files.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- rust
- 領域
- testing, tooling
- issue の種類
- リファクタリング
- 難易度
- 2/5
- 見積もり時間
- 1〜3時間
- 活発さ
- 停滞
- 明瞭さ
- 明確に書かれている
- 初心者へのやさしさ
- 65/100