ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #qtest
A technical decision guide for selecting between manual and automated test execution in qTest Manager, including API implementation and trade-off analysis.
Learn how to separate Planned and Execution Test Cycles in qTest Manager to keep reporting clean and quality gates accurate.
Pushing CI test results into qTest via its REST API unifies manual and automated coverage — but the real work is stable ID mapping and idempotent submission, not the API call itself.
Decide whether to run tests in qTest manually, automatically via CI/CD, or mix both. Compare constraints, trade‑offs, and see a concrete REST‑API upload example.
We need to migrate a small application’s test artifacts from an existing qTest instance to a new deployment while keeping the system online. The goal is to preserve continuity for both test execution and defect tracking in Jira. The primary constraint is the lack of a single‑transaction migration path. qTest’s REST API supports incremental pulls via the modi
Goal is to keep operational alerts useful without notification noise in QTest. QTest offers per-user notification subscriptions for project events such as test runs, requirements changes and defects. Controls are managed through user profile and project subscription settings with opt-in per object type and role. Delivery is limited to objects the user can ac
Goal Prevent accidental exposure of test artifacts by revoking or expiring public URLs once the Public Access toggle is disabled. Current State Enabling the Public Access toggle creates a permanent read‑only URL that remains valid until the toggle is turned off. However, disabling the toggle does not invalidate URLs that have already been generated; they con
jira