DOCSEARCHbyAlgolia
Submit Docs

Test IO Integration Guides

website·Indexed 29 days ago

https://test-guides.vercel.app

Documentation for integrating Test IO with external platforms, including detailed guides for the Jira Cloud and Jira Data Center (Server) plugins and the Test IO Zapier app. Covers bug report synchronization, exploratory test management, workflow automation using triggers and actions, and migration from Atlassian Server to Cloud.

Tokens
20.2K
Snippets
19
Records
154
Agent score
74%

What's inside Test IO

  1. Overview of Test IO integration options

    Test IO provides several ways to connect its testing platform with external development and project management ecosystems:

    • Bug Trackers: Export bugs reported by testers directly into systems such as Jira and GitHub.
    • Test Case Managers: Execute tests using cases imported from managers like TestRail and Xray.
    • Jira Add-ons: Dedicated plugins for Jira Cloud and Jira Server (Data Center) to run tests and review bugs within the Jira interface.
    • Zapier: Automate workflows and receive notifications about test cycle changes across thousands of supported apps.
    • Customer API: Build bespoke integrations using the provided Customer API.
    • Custom Integrations: Request a tailored integration if existing options do not meet specific needs.

  2. Overview of QA Service for Jira

    The QA Service for Jira is an integration that connects a Jira instance to Test IO's network of professional testers. It allows users to execute test cases, perform exploratory tests, and verify bugs on real devices and browsers. Key capabilities include receiving detailed bug reports (with screencasts and reproduction steps) directly in Jira and maintaining two-way synchronization between Jira and the Test IO platform. A Test IO subscription is required to use the features, although the app can be installed without one.

  3. Overview of Test IO Zapier Integration

    The Test IO Zapier integration allows users to connect the Test IO platform to over 5,000 other popular apps via Zapier. This enables the automation of workflows (Zaps) to monitor for new or updated data, find existing data, or create and update data within Test IO, such as receiving immediate notifications about changes in test cycles.

  4. Overview of QA Service for Jira

    The QA Service for Jira plugin integrates a Jira instance with the Test IO network of professional testers. This allows users to execute test cases, perform exploratory tests, and verify bugs on real devices and browsers. Key capabilities include receiving detailed bug reports (with screencasts and reproduction steps) directly in Jira and managing workflows via a two-way synchronization between Jira and the Test IO platform. Note: While the app can be installed by anyone, a Test IO subscription is required to use its features.

  5. Understand and identify bug reproduction types in Jira Cloud

    In the context of Test IO bugs, a bug reproduction is the process of retesting a reported bug to verify its existence. There are two outcomes:

    • Positive Reproduction: The bug is encountered again by following the original report's steps.
    • Negative Reproduction: The bug cannot be reproduced, suggesting the functionality works correctly on the tester's specific environment.

  6. Monitor Test IO Exploratory Tests in Jira Cloud

    The Jira Cloud Plugin allows users to view and monitor Test IO exploratory tests created on either the Jira or Test IO platforms. Users can track tests with statuses such as Customer Finalized, Waiting, and Running.

    Available test details include:

    • Start and End Date: The scheduled time frame for the test.
    • Test IO Product and Section: The associated product and section.
    • Included Features: List of features under test.
    • Devices and Environment: Hardware and software environments used.
    • Test Goal: The primary objective of the test.
    • Out of Scope: Aspects explicitly excluded from the test session.
    • Requirements: Specific criteria needed for the test.

    The plugin also provides a filtering option to sort tests by their current status.

  7. View and monitor Test IO exploratory tests in Jira

    The Jira Data Center (Server) Plugin allows users to view and monitor Test IO exploratory tests (created on either Jira or the Test IO platform) directly within Jira. Supported test statuses include Waiting, Running, Initialized, and Customer Finalized.

    Available test details include:

    • Start and End Date
    • Test IO Product and Section
    • Included Features
    • Devices and Environment
    • Test Goal
    • Out of Scope items
    • Requirements

  8. Retrieve bug details using Test IO Zapier Searches

    The Test IO Zapier App offers two ways to find bug information:

    1. Fetch Bug: Retrieves detailed information about a bug using its internal Test IO bug ID.
    2. Fetch Test IO Bug by External ID: Locates a bug using its ID from an external tracking system (e.g., using a Jira Issue Key from Jira Cloud). This is specifically useful when a bug has been exported to an external tracker and the original Test IO ID is unknown.

  9. Understand bug reproduction types in Jira Server

    Bug reproduction involves retesting a bug reported by another tester to verify its existence. There are two outcomes:

    • Positive Reproduction: The bug is encountered by following the original report's steps.
    • Negative Reproduction: The bug cannot be reproduced following the same steps, meaning the functionality works correctly on the tester's device.

  10. Understand Test IO Jira connection types

    The Jira Data Center (Server) Plugin supports two types of connections to link Jira with Test IO accounts:

    1. Global (default) Connection: Applies globally across all Jira projects in the instance. Only one Global connection can exist, and it is inactive by default.
    2. Project-Specific Connection: Links a specific Jira project to a Test IO account. This is used when a project requires a different configuration than the global default or when integration is only needed for a single project.

  11. Integrate Test IO with Jira Server or Cloud

    The Test IO Jira App allows users to access Test IO capabilities directly within Jira. Key functionalities include connecting Jira boards, running tests, reviewing and exporting bugs to the backlog, and requesting bug fix confirmations. Depending on your infrastructure, you must use the specific plugin for either Jira Server (Data Center) or Jira Cloud.

  12. Triage open bugs using the Received Bugs view

    The 'Received Bugs' page lists open bugs from configured Test IO Products and Sections that require triage.

    Filtering Options:

    • Severity: Filter by Test IO bug severities.
    • Product: Filter by configured Test IO Products with open bugs.
    • Feature: Filter by Test IO Features with open bugs.
    • Test Cycle: Filter by Test IO Test Cycles with open bugs.

    Bug Details View: Selecting a bug from the list expands a detail panel on the right containing:

    • Action Buttons: Accept, Reject, Send Request, Change Severity, Confirm Bug, and Leave Comment (availability depends on the customer pricing plan; some are located under the 'More' dropdown).
    • Bug Description: Includes Steps to reproduce, Actual result, and Expected result.
    • Attachments: Section for bug-related files.
    • Bug Report Confirmation: Displays details of requests for confirmation sent from Jira.
    • Bug Reproductions: Lists other testers and devices that reproduced the bug.
    • Comments: History of actions (e.g., rejection reasons, severity change comments, tester answers).