rabelenda opened a new issue, #9270: URL: https://github.com/apache/devlake/issues/9270
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar feature requirement. ### Use case As a QA or engineering lead using Zephyr Scale Cloud with Jira, I want DevLake to collect test cases, cycles, and executions so I can see pass rate, execution time, and test activity alongside the rest of our delivery data. DevLake has a QA domain and no Zephyr data source. ### Description Add a Zephyr Scale Cloud plugin for the Zephyr Scale REST API v2. A scope is one enabled Jira project (scope id is the project key). Connection: * Endpoint. Default https://api.zephyrscale.smartbear.com/v2. EU: https://eu.api.zephyrscale.smartbear.com/v2 * API access token (Bearer), from Jira → Profile → Zephyr Scale API Access Tokens Collected data: * Folders, test cases, test case labels, and test case links to Jira issues * Test cycles * Test executions and execution links to Jira issues Domain mapping, using the QA domain from #8393: * Jira project → qa_projects * Test case → qa_test_cases (name, created time, owner, and type). Type comes from a scope-config custom field, default name Test Type. When that field is empty, the type is functional. * Test execution → qa_test_case_executions (linked test case, start and finish time, executor, status) Execution status: * Pass / Passed → SUCCESS * Fail / Failed / Blocked → FAILED * In Progress / Executing → IN_PROGRESS * Any other status, including empty → PENDING Time range: * Executions use the API filter actualEndDateAfter. * The test case and test cycle list APIs have no date filter. A full sync keeps cases created on or after the project time, and cycles whose planned start is on or after that time. An incremental sync recollects cases and cycles so later edits are kept. Folders, priorities, statuses, cycles, labels, Jira issue links, estimated time, execution time, and the automated flag stay in the tool tables. The Grafana dashboards use them. They are not separate domain entities. Config UI: beta plugin, connection form, Jira project scope picker, and a transformation field for the test-type custom field. Collected entity: CODEQUALITY. Dashboards: MySQL (zephyr-dashboard) and PostgreSQL (zephyr-dashboard-pg). They show execution totals, pass rate, average execution time, automated share, status distribution, test cases by priority, status, and folder, cycles by status, and recent executions. This version is Zephyr Scale Cloud. It does not collect Zephyr Squad, Zephyr Scale Server or Data Center, test steps, or accounts as their own domain entity. ### Related issues #8393 ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
