Skip to content

Commit a175f00

Browse files
committed
Add .ai_context directory for AI-assisted test generation
1 parent d436871 commit a175f00

File tree

1 file changed

+25
-0
lines changed

1 file changed

+25
-0
lines changed

.ai_testgen/README.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
# AI-Assisted Test Generation
2+
3+
This proposal aims to integrate an AI-assisted test generation system into the Hive upstream repository.
4+
To achieve this, we suggest creating a dedicated directory `.ai_testgen` within the repository to store prompt files and related resources.
5+
This ensures that contributors who already have the Hive repository can directly leverage these assets without the need to clone or maintain a separate repository.
6+
7+
## Two possible implementation options are described below:
8+
9+
**1. Clone external repository**
10+
- Migrate the contents of `[email protected]:huangmingxia/test-generation-assistant.git` into the `.ai_testgen` folder.
11+
```bash
12+
git clone [email protected]:huangmingxia/test-generation-assistant.git
13+
```
14+
- Populate `.ai_testgen/config/rules` with upstream-specific rules to be used for generating test cases and end-to-end (e2e) tests.
15+
16+
17+
**2. Rules-only integration**
18+
- Only add the `rules/` directory inside `.ai_testgen/rules`.
19+
- Configure test case or e2e generation to load these rules by default.
20+
**Limitation**:
21+
- For pre-merge testing, `jira-mcp-snowflake` currently lacks support for extracting associated PR links from Jira issues.
22+
- Additionally, DeepWiki is updated on a weekly basis, which means that code changes within this interval cannot be retrieved.
23+
24+
### Recommended approach [TBD]
25+
Currently recommend approach 1 (cloning the external repository), as it ensures all code changes, including pre-merge changes, are available during test generation.

0 commit comments

Comments
 (0)