Add GitNexus integration test scenarios for CTORNDGAIN-1494.#92
Conversation
TestRail-compatible cases covering GitNexus MCP validation (20 scenarios). Co-authored-by: Cursor <cursoragent@cursor.com>
| - After step 5: Agent runs `npx gitnexus@latest setup` | ||
| - After step 6: Both commands complete without errors | ||
| - After step 7: `.gitnexus/` directory exists in PROJECT (verify with `ls -la .gitnexus/`). Phase 6 logged as "installed" in state file | ||
|
|
There was a problem hiding this comment.
I would also add that gitnexus is added to MCP config.
After running /mcp, gitnexus · ✔ connected would be received
| **Expected Results**: | ||
| - After step 4: GitNexus appears in the MCP server list | ||
| - After step 5: Status shows GitNexus as connected/active | ||
| - After step 8: `gitnexus_query()` returns results (symbols, processes) without errors. This confirms healthy handshake (Assumption A-1) |
There was a problem hiding this comment.
I would check that not particularly gitnexus_query() is called but if any gitnexus tools were used. Please check gitnexus tools here: https://github.com/griddynamics/rosetta/blob/v3/instructions/r3/core/skills/gitnexus-tools/SKILL.md
| 4. Wait for Phase 7 (Documentation) to complete | ||
| 5. Check if `.gitnexus/` exists: `ls .gitnexus/` | ||
| 6. Open `CONTEXT.md` and search for "GitNexus", "gitnexus-tools", "gitnexus-cli" | ||
| 7. Open `gain.json` and search for "gitnexus" |
There was a problem hiding this comment.
Integration to gain.json wasn't implemented
| 5. When Phase 6 asks about GitNexus — answer **Yes** | ||
| 6. Wait for all phases to complete (through Phase 9 — Verification) | ||
| 7. Verify `.gitnexus/` exists: `ls -la .gitnexus/` | ||
| 8. Open `gain.json` and look for a GitNexus integration entry |
There was a problem hiding this comment.
Integration to gain.json wasn't implemented. It shouldn't be checked
|
|
||
| --- | ||
|
|
||
| ### TC-009: MCP clean shutdown — no orphaned processes (Happy Path) |
There was a problem hiding this comment.
I don't think that it should be checked
There was a problem hiding this comment.
I'll remove TC-009. Thanks!
| --- | ||
|
|
||
| ### TC-011: `gain.json` contains GitNexus entry after opt-in (Happy Path) | ||
|
|
There was a problem hiding this comment.
It shouldn't be tested
There was a problem hiding this comment.
I'll remove TC-011. Thanks!
| --- | ||
|
|
||
| ### TC-012: Removing GitNexus from `gain.json` disables integration (Negative) | ||
|
|
There was a problem hiding this comment.
It shouldn't be tested
There was a problem hiding this comment.
I'll remove TC-012. Thanks!
| | AC-3: GitNexus failure never blocks Rosetta | TC-006 | | ||
| | AC-4: `gain.json` is single source of truth | TC-011, TC-012 | | ||
| | AC-5: CONTEXT.md sufficient for agent discovery | TC-013 | | ||
| | AC-6: Consistent across agents | All TCs (agent-agnostic by design — run suite on each agent tool) | |
There was a problem hiding this comment.
I think the list of AI Editors in which gitnexus must be tested should be specified.
There was a problem hiding this comment.
I'll execute all Test Cases in all Agentic Tools. I asked TestGen not to specify list of tools as it could be changed in the future. I'll fix summary of the doc to reflect that ALL test cases should be executed on ALL supported AI Tools.
| | AC-4: `gain.json` is single source of truth | TC-011, TC-012 | | ||
| | AC-5: CONTEXT.md sufficient for agent discovery | TC-013 | | ||
| | AC-6: Consistent across agents | All TCs (agent-agnostic by design — run suite on each agent tool) | | ||
|
|
There was a problem hiding this comment.
I think it would be also good to add - checking gitnexus in rosetta local mode and in rosetta plugin mode.
In local mode - gitnexus installed successfully, indexed codebase, gitnexus tools are used. But in case of any changes the index would be updated only after commits
In plugin mode - gitnexus installed successfully, indexed codebase, gitnexus tools are used. In case of any changes the index would be updated just after any code modifications
What do you think about it?
There was a problem hiding this comment.
I'll add test cases for this. Thanks!
Remove gain.json tests, add MCP and mode-specific cases, and align coverage with current implementation. Co-authored-by: Cursor <cursoragent@cursor.com>
3 participants
TestRail-compatible cases covering GitNexus MCP validation (20 scenarios).