@bun913/mcp-testrail 0.19.1 → 0.19.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -45,6 +45,17 @@ You can connect this MCP server by setting like the below. This method uses `npx
|
|
|
45
45
|
- **`spawn node ENOENT` errors**: Ensure that Node.js is properly installed and in your PATH.
|
|
46
46
|
- **Authentication issues**: Check your TestRail API credentials.
|
|
47
47
|
- **Your conversation is too long**: Use `limit` and `offset` parameters for test cases and sections to paginate results.
|
|
48
|
+
- **HTTP 400 errors when creating/updating test cases**: TestRail projects have different templates, custom fields, and required fields. This MCP server passes your parameters directly to the TestRail API — it does not validate or transform them. If you encounter 400 errors, define your project's rules in `CLAUDE.md` or `AGENTS.md` so the LLM sends the correct parameters. For example:
|
|
49
|
+
|
|
50
|
+
```markdown
|
|
51
|
+
# TestRail Rules for This Project
|
|
52
|
+
- Project ID: 1
|
|
53
|
+
- Always use template 2 (Separated Steps) when creating test cases
|
|
54
|
+
- Use `customStepsSeparated` (array of step objects)
|
|
55
|
+
- Do NOT send `customSteps` or `customExpected` with template 2
|
|
56
|
+
- Required custom fields: custom_automation_type (default: 0)
|
|
57
|
+
- Call `getCaseFields` at the start of a session to check available fields
|
|
58
|
+
```
|
|
48
59
|
|
|
49
60
|
## Contributing
|
|
50
61
|
|