DOCSEARCHbyAlgolia
Submit Docs

Test IO Documentation

website·Indexed 35 days ago

https://guides.test.io

Guides and API reference for the Test IO platform, including REST API documentation for managing exploratory tests, test cases, and features. Includes integration guides for Jira Cloud, Jira Server (Data Center), Notion, and Zapier, covering bug triaging, synchronization, and workflow automation.

Tokens
33.8K
Snippets
98
Records
267
Agent score
49%

What's inside Test IO

  1. Overview of Custom Bug Export Connections

    Custom Bug Export Connections allow you to expose an HTTPS endpoint that receives a JSON bug payload whenever a bug is exported via the customer interface (either by a user action or via auto-export). This provides a flexible alternative to native integrations for any tracker or workflow system that can accept an HTTP POST request. Common trackers used with this method include Jira, GitHub, GitLab, Azure DevOps, Linear, Trello, and Zendesk.

  2. 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) by monitoring for new or updated data in Test IO, finding existing data, or creating and updating data within the Test IO platform.

  3. Overview of Test IO Zapier triggers

    The Test IO Zapier app provides several triggers to automate workflows based on events occurring within the Test IO platform. Available triggers include bug report approvals, exports, exploratory test cycle status changes, bug fix confirmation updates, and new comments on bug reports.

  4. Overview of QA Service for Jira integration

    The QA Service for Jira integrates a Jira instance with Test IO's 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 within Jira and maintaining two-way synchronization between the Jira interface and the Test IO platform. Note: While the app can be installed by anyone, a Test IO subscription is required to utilize its features.

  5. Retrieve bug details in Test IO via Zapier

    The Test IO Zapier App offers two search methods to retrieve 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 in Test IO using an ID from an external tracking system. This is specifically useful when a bug has been exported to a system like Jira and the original Test IO ID is unknown.
    Example for Fetch Test IO Bug by External ID:
- Bug tracker: Jira Cloud
- External ID: Jira Issue Key

  6. Integrate Test IO with external tools

    Test IO provides several integrations to streamline bug tracking and workflow automation:

    • Notion: Export bugs from Test IO to a Notion database.
    • Jira: Connect with Jira Cloud or Jira Data Center for bug tracking.
    • Zapier: Automate workflows by connecting Test IO with over 5,000 other applications.

  7. View and monitor Test IO Exploratory Tests in Jira Cloud

    The Jira Cloud Add-On allows users to view and monitor exploratory tests created on either the Jira or Test IO platforms. Supported test statuses include Customer Finalized, Waiting, Locked, and Running. Each test record provides the following details:

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

  8. Filter and navigate User Story execution lists

    The 'User Stories' page provides tools to manage the visibility of execution data:

    Navigation Controls:

    • Expand All Rows / Collapse All Rows: Simultaneously expand or collapse all user stories for a quicker overview.
    • View Levels: Results can be viewed at the Product Level (overall counts), Feature Level (associated stories), or User Story Level (individual status).

    Filtering Options:

    • Product: Filter by the associated product.
    • Test environment: Filter by the specific environment.
    • Test cycle: Filter by the execution cycle.
    • Date range: Filter by a specific timeframe.
    • Clear: Use the 'Clear' button to remove all active filters and return to the default preview.

  9. Understand and manage Test Templates

    Test Templates allow you to save a successful test setup for reuse in future tests. They can be selected during test setup, named for clarity, and deleted individually. There is a limit of 10 templates per product. Test templates can serve as an alternative to features when creating exploratory tests. To use them, you must first have a product created.

  10. Understand Test IO Jira connection types

    The Jira Data Center Add-On supports two types of connections to link Jira with Test IO:

    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 unique configuration or when integration is only needed for a single project.

  11. Available test IO API resources

    The test IO REST API provides access to the following resources:

    • Binary Apps: Upload and manage binary application files
    • Connections: Manage connections
    • User Stories: Create and manage user stories
    • User Story Version Executions: List execution results for user stories
    • Features: List and create features
    • Bugs: Fetch, search, and manage bugs
    • Exploratory Tests: Create and manage exploratory tests
    • Test Cases: Create test cases
    • Products: Manage products
    • Test Case Tests: Create test case tests
    • Test Environments: Manage test environments
    • Test Templates: List test templates
    • Bug Report Confirmations: Create bug report confirmations
    • Access Claims: Create and manage access claims groups and test accounts

  12. Access Test IO integration settings in Jira

    Once the QA Service for Jira add-on is installed, a Test IO section appears in the left-side navigation menu under Apps. This section contains three subsections required to enable the integration:

    • Connection: Used to connect your Test IO account to Jira.
    • Configuration: Used to configure the integration between Jira and the Test IO platform.
    • Maintenance: General maintenance settings.