NektonIntegrationsIT Operations Test IO

Test IO Test IO Test IO integration with Test IO

How to Accepting bugs in test IO after new exploratory tests end in test IO

  4.6/5 from 8 votes. About 5 minutes to complete.

Steps to automate

Use workflow automation service.
Preparation
Create Nekton account. You can also use your existing Google account to sign in.
Create automation
  • Click on the "Create new workflow" button, and then add "Automated step".
  • Set the step description to "Accepting bugs in test IO after new exploratory tests end in test IO" and then click on "Automate".
  • Provide the necessary parameters and click on the "Test it" button to check your automation. If you had issues with it, you can click on "Automate" again to try a different one.
Create a schedule (optional)
If you want to run this automation on a schedule, click on the gear button on the workflow editor screen to configure it. For example, you can run this flow every hour or every day.

Automate Test IO integrations

Test IO actions

Nekton can use any feature that is available in Test IO API. Using our advanced AI, you can easily create custom automations for Test IO. Here are some typical actions you can do in your automated workflows.
Accept Bug
Accepts a bug.
Reject Bug
Rejects a bug.
Inquiry Bug
Inquiries information about a bug.
Fetch Bug
Fetches bug attributes.
Bug Fix Confirmation Status Changed
Triggers when status of bug fix confirmation changed.
Bug Report Forwarded to Customer
Triggers when a bug is forwarded to customer.

About Test IO

Test.io provides a comprehensive range of expertise across multiple areas of software QA testing