import-test-results-xray
Skill28 starsChanged 4 months agoMITView on GitHub
Đẩy kết quả test automation (Playwright/JUnit/Allure) lên Xray Test Management.
- Reads credentials
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- analyze-flaky-testsSkill
- analyze-requirement-documentSkill
- fetch-jira-requirementsSkill
- flaky-test-analyzerSkill
- framework-architectSkill
- generate-api-tests-from-swaggerSkill
- generate-application-test-planSkill
- generate-automation-frameworkSkill
- generate-automation-from-testcasesSkill
- generate-automation-from-ui-flowSkill
- generate-combinatorial-test-dataSkill
- generate-cross-module-test-planSkill
- generate-locatorSkill
- generate-manual-testcases-rbtSkill
- generate-requirements-from-websiteSkill
- generate-testcases-from-requirementsSkill
- generate-test-dataSkill
- jira-integrationSkill
- locator-healer-agentSkill
- qa-automation-engineerSkill
- rbt-manual-testingSkill
- requirements-analyzerSkill
- smart-locator-agentSkill
- test-data-generatorSkill
- ui-debug-agentSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 53
Test Key Convention: Test title nên chứa Jira key để Xray mapping tự động:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Workflow: Import Test Results to Xray
BẮT BUỘC (MANDATORY SKILL): Bạn PHẢI nạp và đọc kỹ nội dung của skill
$jira-integration(tại.agents/skills/jira-integration/SKILL.md) để biết cách sử dụng scripts trước khi bắt đầu.
Workflow này giúp đẩy kết quả test automation lên Xray (Cloud hoặc Server/Data Center) để tracking trên Jira.
Các bước thực hiện:
- Kiểm tra prerequisites:
- Đọc skill
$jira-integrationđể nắm cấu trúc scripts. - Kiểm tra file
.envđã cấu hình Xray credentials:- Xray Cloud:
XRAY_CLIENT_ID,XRAY_CLIENT_SECRET - Xray Server:
JIRA_PAThoặcJIRA_EMAIL+JIRA_API_TOKEN
- Xray Cloud:
- Kiểm tra
XRAY_PLATFORM(cloud/server) trong.env. - Nếu chưa cài dependencies:
cd scripts/integrations && npm install
- Đọc skill
- Verify Xray authentication:
node scripts/integrations/jira/xray_auth.js --verify- Nếu thất bại: kiểm tra credentials trong
.env
- Nếu thất bại: kiểm tra credentials trong
- Xác định report cần import:
- Hỏi user loại report:
- Playwright JSON:
--format playwright --file <path-to-results.json> - JUnit XML:
--format junit --file <path-to-junit.xml> - Xray JSON (đã convert sẵn):
--format xray --file <path-to-xray.json>
- Playwright JSON:
- Xác nhận Project Key (từ
.envhoặc--project)
- Hỏi user loại report:
- Thực thi import:
# Playwright report node scripts/integrations/jira/xray_importer.js --format playwright --file ./test-results.json --project PROJ # JUnit XML node scripts/integrations/jira/xray_importer.js --format junit --file ./junit-results.xml --project PROJ # Xray JSON node scripts/integrations/jira/xray_importer.js --format xray --file ./xray-payload.json - Xử lý kết quả:
- Kiểm tra output: Test Execution Key được tạo trên Jira.
- Nếu thành công: thông báo user key của Test Execution mới.
- Nếu thất bại: đọc log → phân tích nguyên nhân → fix → chạy lại.
- Lưu ý quan trọng:
- Test Key Convention: Test title nên chứa Jira key để Xray mapping tự động:
test('[PROJ-123] Login should work', async ({ page }) => { ... }); - Xray Cloud cần authenticate riêng (Client ID + Secret), khác với Jira auth.
- Rate limit: Tránh import quá nhiều lần liên tiếp.
- Test Key Convention: Test title nên chứa Jira key để Xray mapping tự động:
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

